lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160113.145354.1680040047047045639.davem@davemloft.net>
Date:	Wed, 13 Jan 2016 14:53:54 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	gregory.clement@...e-electrons.com
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	thomas.petazzoni@...e-electrons.com, f.fainelli@...il.com,
	jason@...edaemon.net, andrew@...n.ch,
	sebastian.hesselbarth@...il.com,
	linux-arm-kernel@...ts.infradead.org, alior@...vell.com,
	nadavh@...vell.com, mw@...ihalf.com, simon.guinot@...uanux.org,
	ezequiel.garcia@...e-electrons.com,
	maxime.ripard@...e-electrons.com,
	boris.brezillon@...e-electrons.com, linux@....linux.org.uk,
	w@....eu, arnd@...db.de
Subject: Re: [PATCH net-next 00/10] Proposal for a API set for HW Buffer
 management

From: Gregory CLEMENT <gregory.clement@...e-electrons.com>
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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ