From: Ben Hutchings <bhutchings@solarflare.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: Should "N/A" dust bunnies be swept from fw_version?
Date: Fri, 18 Nov 2011 00:19:34 +0000 [thread overview]
Message-ID: <1321575574.2749.55.camel@bwh-desktop> (raw)
In-Reply-To: <4EC5984D.5070501@hp.com>
On Thu, 2011-11-17 at 15:27 -0800, Rick Jones wrote:
> In the discussion on "enable virtio_net to return bus_info in ethtool -i
> consistent with emulated NICs" Ben Hutchings had the following feedback
> on what might go into bus_info:
>
> > Please use the existing 'not implemented' value, which is the empty
> > string. If you think ethtool should print some helpful message instead
> > of an empty string, please submit a patch for ethtool.
>
> When I was sweeping in the .get_drvinfo routines, I noticed many drivers
> would return "N/A" for fw_version - presumably they were drivers for
> cards without firmware. Should those be removed to have the fw_version
> be the empty string, or should those sleeping dust bunnies be allowed to
> lie?
I much prefer the empty string; the ethtool utility can turn that into a
user-friendly placeholder if it's considered confusing.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-11-18 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 23:27 Should "N/A" dust bunnies be swept from fw_version? Rick Jones
2011-11-18 0:19 ` Ben Hutchings [this message]
2011-11-18 19:09 ` Rick Jones
2011-11-18 19:10 ` David Miller
2011-11-18 19:23 ` Rick Jones
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=1321575574.2749.55.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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).