linux-kernel - Re: pull request: linux-firmware: update cxgb* firmwares

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:	Sun, 19 Feb 2012 01:04:15 +0000
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Divy Le Ray <divy@...lsio.com>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org, Neil Horman <nhorman@...driver.com>
Subject: Re: pull request: linux-firmware: update cxgb* firmwares

On Sun, 2012-02-19 at 00:58 +0000, Ben Hutchings wrote:
> On Fri, 2012-02-17 at 11:30 -0800, Divy Le Ray wrote:
> > On 2/16/2012 7:41 PM, Ben Hutchings wrote:
[...]
> > > Are there any versions of the cxgb4 driver that will specifically
> > > request cxgb4/t4fw-1.3.10.0.bin?  If not, what's the point of keeping it
> > > around after changing the cxgb4/t4fw.bin symlink?
> > 
> > Hi Ben,
> > 
> > I originally removed cxgb4/t4fw-1.3.10.0.bin when I posted the request 
> > against David's tree.
> > Subsequent review from Neil requested to keep it around at least for a 
> > while (https://lkml.org/lkml/2012/2/11/61).
> > Either way is fine to me.
> 
> No, Neil said you need to maintain cxgb4/t4fw.bin, but it's perfectly
> fine for that to be a symlink.

So I've pulled your changes and then deleted the cxgb4/t4fw-1.3.10.0.bin
as a separate commit.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)