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]
Date:	Thu, 17 Mar 2016 14:10:17 +0100
From:	Giuseppe CAVALLARO <peppe.cavallaro@...com>
To:	David Miller <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, <gabriel.fernandez@...aro.org>,
	<afaerber@...e.de>, <fschaefer.oss@...glemail.com>,
	<dinh.linux@...il.com>, <preid@...ctromag.com.au>
Subject: Re: [PATCH (net-next.git) 0/2] STMMAC: MDIO settings

On 3/16/2016 11:09 PM, David Miller wrote:
>
> Don't _ever_ send the same two sets of patches targetting net and
> net-next at the same time.

cover-letter reports the difference between the two patches for
net and next.

> Especially right now, as 'net' is basically frozen, and 'net-next' is
> closed for new features and is only for last minute bug fixes before I
> send a merge window pull request to Linus.

I do think that:

     [PATCH (net-next.git) 0/2] STMMAC: MDIO settings
     [PATCH (net-next.git)] stmmac: fix TX normal DESC

are last minute bug fixes for net-next.

Peppe

>
> I'm tossing both of these series, figure it how to do this properly.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ