linux-kernel - Re: [PATCH 0/3] Net driver bugs fix and code style

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: <20160426.135737.253524112795921967.davem@davemloft.net>
Date:	Tue, 26 Apr 2016 13:57:37 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	noamca@...lanox.com
Cc:	linux-kernel@...r.kernel.org, abrodkin@...opsys.com,
	eladkan@...lanox.com, talz@...lanox.com
Subject: Re: [PATCH 0/3] Net driver bugs fix and code style

From: Noam Camus <noamca@...lanox.com>
Date: Tue, 26 Apr 2016 17:23:26 +0000

>>From: David Miller <davem@...emloft.net>
>>Sent: Tuesday, April 26, 2016 6:57 PM
>>
>>Bug fixes must be targetted at the 'net' tree, and anything else
>>must be targetted at the 'net-next' tree.
> Should we handle bugs fix first (more urgent then code style) and once it will be accepted and applied to net-next proceed with the code style patch?

That's exactly what I am telling you, yes.