From: David Miller <davem@davemloft.net>
To: raj@tardy.cup.hp.com
Cc: jcliburn@gmail.com, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, dm@chelsio.com, sbhatewara@vmware.com,
ron.mercer@qlogic.com, chris.snook@gmail.com, divy@chelsio.com
Subject: Re: [PATCH net-next] Sweep away N/A fw_version dustbunnies from the .get_drvinfo routine of a number of drivers
Date: Tue, 22 Nov 2011 16:53:37 -0500 (EST) [thread overview]
Message-ID: <20111122.165337.867376721899719922.davem@davemloft.net> (raw)
In-Reply-To: <20111121205405.A0FF1290041F@tardy>
From: raj@tardy.cup.hp.com (Rick Jones)
Date: Mon, 21 Nov 2011 12:54:05 -0800 (PST)
> From: Rick Jones <rick.jones2@hp.com>
>
> Per discussion with Ben Hutchings and David Miller, go through and
> remove assignments of "N/A" to fw_version in various drivers'
> .get_drvinfo routines. While there clean-up some use of bare
> constants and such.
>
> Signed-off-by: Rick Jones <rick.jones2@hp.com>
Applied, thanks Rick.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2011-11-22 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 20:54 [PATCH net-next] Sweep away N/A fw_version dustbunnies from the .get_drvinfo routine of a number of drivers Rick Jones
2011-11-22 21:53 ` David Miller [this message]
2011-11-22 22:22 ` Francois Romieu
2011-11-22 22:35 ` Rick Jones
2011-11-23 0:32 ` 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=20111122.165337.867376721899719922.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chris.snook@gmail.com \
--cc=divy@chelsio.com \
--cc=dm@chelsio.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jcliburn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=raj@tardy.cup.hp.com \
--cc=ron.mercer@qlogic.com \
--cc=sbhatewara@vmware.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).