From: Rick Jones <rick.jones2@hp.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Divy Le Ray <divy@chelsio.com>,
David Woodhouse <dwmw2@infradead.org>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Steve Wise <swise@opengridcomputing.com>,
nhorman@tuxdriver.com
Subject: Re: [patch net-next] cxgb3: update firmware version
Date: Tue, 14 Feb 2012 10:17:27 -0800 [thread overview]
Message-ID: <4F3AA537.4050700@hp.com> (raw)
In-Reply-To: <4F39F75D.6030107@chelsio.com>
What does an end-user/customer see and do? When they are told that
version the firmware, specified down to the fix level, fixes a problem
they are having, how will they know that firmware blob filename
drvfw-X.bin on a download/archive site has that fix? Yes, the support
folks can say "It is the drcfw-X.bin file which is 12345 bytes in size
with the MD5sum of <blah> but the principle of the telephone game
dictates the size and/or MD5sum information will drop as "the word"
passes from one person to another. And one cannot run
ethtool_ops::get_drvinfo against a website. Two versions may indeed be
"compatible" in terms of interfaces, but they won't be identical in
terms of desirability. As such, for them to be contained in files with
identical names just seems like asking for confusion.
Firmware is something of a tiny kernel no? Would we have everyone name
vmlinux files with just a major number?
rick jones
next prev parent reply other threads:[~2012-02-14 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 20:28 [patch net-next] cxgb3: update firmware version Divy Le Ray
2012-02-13 20:43 ` David Woodhouse
2012-02-13 21:39 ` Divy Le Ray
2012-02-14 1:59 ` Ben Hutchings
2012-02-14 4:49 ` Divy Le Ray
2012-02-14 5:08 ` Ben Hutchings
2012-02-14 5:55 ` Divy Le Ray
2012-02-14 18:17 ` Rick Jones [this message]
2012-02-14 18:21 ` Ben Hutchings
2012-02-14 20:02 ` Rick Jones
2012-02-14 22:02 ` Ben Hutchings
2012-02-15 20:48 ` David Miller
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=4F3AA537.4050700@hp.com \
--to=rick.jones2@hp.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=divy@chelsio.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.