netdev - RE: [PATCH net 00/10] qed*: Bug fixes

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: <BL2PR07MB23065BFB31B2BC1031663D7D8D5E0@BL2PR07MB2306.namprd07.prod.outlook.com>
Date:   Mon, 20 Feb 2017 20:14:17 +0000
From:   "Mintz, Yuval" <Yuval.Mintz@...ium.com>
To:     David Miller <davem@...emloft.net>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net 00/10] qed*: Bug fixes

 > > Hi Dave,
> >
> > The 3 first patches here are a repost of
> > ("qed: RoCE infrastructure fixes"). The fourth is an additional
> > RoCE-related infrastructure fix, and the latter contain various fixes
> > to qed/qede.
> >
> > Notice patch #10 will create a conflict when net and net-next would be
> > merged [although its fix is quite trivial].
> >
> > Please consider applying these to `net'.
> 
> Linus made his release so all patches are going into net-next, which this
> series doesn't apply cleanly to.  Please therefore respin your series against
> net-next, thanks.

Just to clarify - do you want me to re-spin the fixes against next-next *now*,
or do you want me to wait until it re-opens? [not sure on its exact state]