From: David Woodhouse <dwmw2@infradead.org>
To: Vlad Zolotarov <vladz@broadcom.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Pushing the new FW to firmware git
Date: Mon, 23 May 2011 16:48:14 +0100 [thread overview]
Message-ID: <1306165695.2627.10.camel@i7.infradead.org> (raw)
In-Reply-To: <201105231813.00751.vladz@broadcom.com>
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
prev parent reply other threads:[~2011-05-23 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 15:12 Pushing the new FW to firmware git Vlad Zolotarov
2011-05-23 15:48 ` David Woodhouse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306165695.2627.10.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=vladz@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).