netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Rick Jones <raj@tardy.cup.hp.com>, netdev@vger.kernel.org
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 14:35:23 -0800	[thread overview]
Message-ID: <4ECC23AB.5060808@hp.com> (raw)
In-Reply-To: <20111122222235.GA24136@electric-eye.fr.zoreil.com>

On 11/22/2011 02:22 PM, Francois Romieu wrote:
> Rick Jones<raj@tardy.cup.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.
>
> Any reason why drivers/net/ethernet/realtek/r8169.c is left in the
> cold ?

No specific reason.  I might not have caught it with my find/grep, or it 
might not have been built in my build environment - after I cloned 
net-next, I brought the .config file from my 64-bit ubuntu virtual 
system to the BE (been bringing it along rather like sourdough starter), 
did a make oldconfig, took all the defaults, did a "make" and then only 
modified those files for which I found the "N/A" in the .c file and 
which had a corresponding .o - that way I "knew" that my changes would 
at least be compiled subsequently and so minimizing the chances of 
incurring davem's wrath by sending him non-compiling code :)

rick jones

  reply	other threads:[~2011-11-22 22:35 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
2011-11-22 22:22 ` Francois Romieu
2011-11-22 22:35   ` Rick Jones [this message]
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=4ECC23AB.5060808@hp.com \
    --to=rick.jones2@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=raj@tardy.cup.hp.com \
    --cc=romieu@fr.zoreil.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).