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

Date:	Mon, 23 May 2011 18:12:59 +0300
From:	"Vlad Zolotarov" <vladz@...adcom.com>
To:	"David Woodhouse" <dwmw2@...radead.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Pushing the new FW to firmware git

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.

Thanks in advance,
vlad

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