netdev - Re: [PATCH net-next V2 0/9] mlx5 driver updates

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: <20160301.145134.1897442242357830301.davem@davemloft.net>
Date:	Tue, 01 Mar 2016 14:51:34 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	saeedm@...lanox.com
Cc:	netdev@...r.kernel.org, ogerlitz@...lanox.com, eranbe@...lanox.com,
	talal@...lanox.com, majd@...lanox.com
Subject: Re: [PATCH net-next V2 0/9] mlx5 driver updates

You guys need to get your act together.

I'm not going to allow two sets of parallel sets of changes to
one driver you guys maintain to be submitted at once.

Period.  I don't care why, or if things don't overlap, you need
to coordinate your submissions strictly.

We have this series, and the one that adds the flower et al.  offload.
Sorry, I'm not going to allow that especially considering what has
happened in the past.

Get one of these accepted first, then you can submit the other one.

I'm tossing all of these changes, resubmit the one you want to be
applied first.

Thanks.