Re: [PATCH net-next 00/10] Proposal for a API set for HW Buffer management

Hi David,
 
 On mar., janv. 12 2016, David Miller [off-list ref] wrote:

If you are going to contribute to netdev you must follow the mailing
list and make not of important announcements such as:

http://marc.info/?l=linux-netdev&m=145248145925834&w=2

I perfectly understand that you are busy during this merge
window. However, I didn't expect a feedback from you but more from the
others who were involved previously on this topic. Moreover, at this
stage I don't expect a deep review but more to start a discussion about
this topic in order to submit a better proposal when the net-ext will be
opened.

I realize that I should not have put you as main recipient. It was
because your address is part of my netdev alias.

Sorry for the inconvenience,

Gregory

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

From: Gregory CLEMENT <redacted>
Date: Wed, 13 Jan 2016 18:36:54 +0100

I perfectly understand that you are busy during this merge
window. However, I didn't expect a feedback from you but more from the
others who were involved previously on this topic.

When a patch is submitted with "net-next" in the Subject line and
no "RFC" or other indication like that, it means you think the
patch is ready for me to consider applying to my tree.

You have to communicate properly in your Subject line tags if you
want me to interpret your changes one way or another.

And quite frankly, I really don't even want to see a lot of RFC
networking changes posted when the merge window is open, I only want
to see bug fixes and people concentrating on that instead of future
work.

Thanks.