From: Sven-Haegar Koch <haegar@sdinet.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Suraj Sumangala <Suraj.Sumangala@atheros.com>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
David Woodhouse <dwmw2@infradead.org>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ?
Date: Sat, 9 Oct 2010 00:47:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1010090040240.19472@aurora.sdinet.de> (raw)
In-Reply-To: <20101008181508.GM10149@tux>
On Fri, 8 Oct 2010, Luis R. Rodriguez wrote:
> > > I last tried to document a thread we had over this here:
> > >
> > > http://wireless.kernel.org/en/developers/Documentation/firmware-versioning
> > >
>
> Thanks, I've updated that link above to document bug fixing does not require
> a filename change.
I would summarize it as:
If a new firmware version also works with an old driver, keep the filename.
If a new firmware version also requires a new driver, change the name.
If a new driver requires a new firmware, change the name.
c'ya
sven-haegar
--
Three may keep a secret, if two of them are dead.
- Ben F.
next prev parent reply other threads:[~2010-10-08 22:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 17:02 Luis R. Rodriguez
2010-10-08 17:27 ` Suraj Sumangala
2010-10-08 18:15 ` Luis R. Rodriguez
2010-10-08 22:47 ` Sven-Haegar Koch [this message]
2010-10-09 8:06 ` Marcel Holtmann
2010-10-12 21:17 ` Henry Ptasinski
2010-10-13 10:06 ` Marcel Holtmann
2010-10-13 17:42 ` Luis R. Rodriguez
2010-10-13 17:54 ` Kevin Hayes
2010-10-13 18:09 ` Luis R. Rodriguez
2010-10-13 18:41 ` Kevin Hayes
2010-10-14 4:23 ` Suraj Sumangala
2010-10-09 8:01 ` Marcel Holtmann
2010-10-11 7:14 ` Senthil Balasubramanian
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=alpine.DEB.2.02.1010090040240.19472@aurora.sdinet.de \
--to=haegar@sdinet.de \
--cc=Luis.Rodriguez@atheros.com \
--cc=Suraj.Sumangala@atheros.com \
--cc=dwmw2@infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=marcel@holtmann.org \
/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
all inboxes | Powered by JetHome®