netdev - Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx

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: <alpine.LFD.2.02.1106141952070.8326@localhost6.localdomain6>
Date:	Tue, 14 Jun 2011 19:52:21 +0100 (BST)
From:	David Woodhouse <dwmw2@...radead.org>
To:	David Miller <davem@...emloft.net>
cc:	mchan@...adcom.com, vladz@...adcom.com, bprakash@...adcom.com,
	eilong@...adcom.com, netdev@...r.kernel.org, dmitry@...adcom.com,
	yaniv.rosner@...adcom.com
Subject: Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx

On Tue, 14 Jun 2011, David Miller wrote:

> > When David Woodhouse integrates the firmware and a new firmware rpm is
> > made available for users, then the new driver will work.

Tarballs are made daily, as soon as the firmware is submitted (which 
doesn't have to wait until the driver is patched). There is no issue with 
bisecting, because any ABI change in the firmware means a *new* firmware 
file which can be instslled in *parallel*.

> This is terrible.

Nonsense. It just means you want to be using an up-to-date copy of the 
firmware, which is hardly a problem.

-- 
dwmw2

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html