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-next>] [day] [month] [year] [list]
Message-ID: <CAOZ2QJOX8JLgCpjohncBhove8zyZ8QMOUGLZHEr-h1D1b-qt7Q@mail.gmail.com>
Date:	Tue, 2 Feb 2016 19:20:12 -0500
From:	Dan Streetman <dan.streetman@...onical.com>
To:	Ariel Elior <ariel.elior@...gic.com>
Cc:	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

Powered by Openwall GNU/*/Linux Powered by OpenVZ