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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 3 Feb 2016 09:58:29 +0000
From:	Ariel Elior <Ariel.Elior@...gic.com>
To:	Dan Streetman <dan.streetman@...onical.com>,
	Yuval Mintz <Yuval.Mintz@...gic.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: RE: bnx2x commits needed to use 7.51.10 firmware?

+Yuval

> -----Original Message-----
> From: Dan Streetman [mailto:dan.streetman@...onical.com]
> Sent: Wednesday, February 03, 2016 2:20 AM
> To: Ariel Elior <Ariel.Elior@...gic.com>
> Cc: netdev <netdev@...r.kernel.org>
> Subject: bnx2x commits needed to use 7.51.10 firmware?
> 
> Hi Ariel,
> 
> I'm trying to update the bnx2x driver in Ubuntu trusty (3.13 kernel)
> release to use the 7.51.10 firmware; can you help me determine which
> commits need to be backported?
> 
> Some reference is in Launchpad bug 1454286:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454286
> 
> basically, there are 87 commits between the current bnx2x driver level
> in Ubuntu trusty's kernel, and commit e42780b where the bnx2x driver
> is acutally updated to use the 7.51.10 firmware.  Can you provide
> guidance to which commits should be pulled back?  Do all 87 of them
> need to be included?
> 
> Thanks!

Powered by blists - more mailing lists