netdev - Re: Pushing the new FW to firmware git

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] [day] [month] [year] [list]

Message-ID: <1306165695.2627.10.camel@i7.infradead.org>
Date:	Mon, 23 May 2011 16:48:14 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Vlad Zolotarov <vladz@...adcom.com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Pushing the new FW to firmware git

On Mon, 2011-05-23 at 18:12 +0300, Vlad Zolotarov wrote:
> David, could u, pls., clarify about the exact procedure of pushing the new FW 
> to the  firwmware git: when exactly the new firware is going to be fetched to 
> the kernel tree? 
> 
> I'm asking it because I am going to submit a patch that introduces a new FW 
> and the new code will simply not work with an old FW. 

OK, so the new firmware gets a new filename, and you submit the new
firmware to the linux-firmware.git tree at the same time as you submit
the code changes to the kernel tree.

-- 
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