From: Johannes Berg <johannes@sipsolutions.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Vipin Mehta <Vipin.Mehta@atheros.com>
Subject: Re: Firmware versioning best practices II
Date: Sat, 20 Feb 2010 12:00:39 +0100 [thread overview]
Message-ID: <1266663639.10357.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1266662106.1820.4034.camel@macbook.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Sat, 2010-02-20 at 10:35 +0000, David Woodhouse wrote:
> That doesn't prevent some people from using foo-$APIVER-$CODEVER if
> they really have to, of course -- if they have firmware which can be
> conditionally compiled for both old and new APIs, for example. But I
> don't think it should be recommended.
That doesn't make much sense anyway. If the firmware filename is
foo-$APIVER-$CODEVER every code change would need a corresponding driver
change. If it is just foo-$APIVER then the $CODEVER can be embedded in
the firmware file and printed so you know which code you're using, but
if it doesn't influence the API I don't see why it should be part of the
filename?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2010-02-20 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 2:23 Luis R. Rodriguez
2010-02-20 10:35 ` David Woodhouse
2010-02-20 11:00 ` Johannes Berg [this message]
2010-02-20 11:09 ` David Woodhouse
2010-02-20 11:10 ` Johannes Berg
2010-02-20 11:32 ` David Woodhouse
2010-02-21 10:13 ` Marcel Holtmann
2010-02-22 19:14 ` Luis R. Rodriguez
2010-02-22 19:27 ` Marcel Holtmann
2010-02-22 21:03 ` Luis R. Rodriguez
2010-02-23 7:06 ` Marcel Holtmann
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=1266663639.10357.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Vipin.Mehta@atheros.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcgrof@gmail.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
all inboxes | Powered by JetHome®