* Pushing the new FW to firmware git
@ 2011-05-23 15:12 Vlad Zolotarov
2011-05-23 15:48 ` David Woodhouse
0 siblings, 1 reply; 2+ messages in thread
From: Vlad Zolotarov @ 2011-05-23 15:12 UTC (permalink / raw)
To: David Woodhouse, netdev@vger.kernel.org
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Pushing the new FW to firmware git
2011-05-23 15:12 Pushing the new FW to firmware git Vlad Zolotarov
@ 2011-05-23 15:48 ` David Woodhouse
0 siblings, 0 replies; 2+ messages in thread
From: David Woodhouse @ 2011-05-23 15:48 UTC (permalink / raw)
To: Vlad Zolotarov; +Cc: netdev@vger.kernel.org
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-05-23 15:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-23 15:12 Pushing the new FW to firmware git Vlad Zolotarov
2011-05-23 15:48 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).