netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [E1000-devel] [PATCH 6/8] e1000e: convert ndev_ printks	to	something smaller
Date: Wed, 02 Apr 2008 11:55:46 -0700	[thread overview]
Message-ID: <47F3D6B2.9070306@intel.com> (raw)
In-Reply-To: <47F12F27.802@intel.com>

Kok, Auke wrote:
> Jeff Garzik wrote:
>> Auke Kok wrote:
>>> From: Bruce Allan <bruce.w.allan@intel.com>
>>>
>>> The ndev_* printk's are too lenghty and we don't need to specify
>>> the adapter/netdev struct at all, making this a lot more readable.
>>>
>>> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
>>> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
>>> ---
>>>
>>>  drivers/net/e1000e/e1000.h   |   27 ++++----
>>>  drivers/net/e1000e/ethtool.c |   38 +++++------
>>>  drivers/net/e1000e/netdev.c  |  148 +++++++++++++++++++-----------------------
>>>  drivers/net/e1000e/param.c   |   31 +++------
>>>  4 files changed, 108 insertions(+), 136 deletions(-)
>> This stuff should just be removed.
>>
>> Either the code should be outputting "ethX: blahblah" via printk(), or 
>> the code should be outputting the standard dev_printk() prefix [driver 
>> name, PCI device info].
>>
>> Also, it is recommended to use the NETIF_MSG_xxx bits to permit 
>> fine-grained control over which messages are output, on a per-port basis 
>> (controlled via ethtool).  grep around for 'msg_enable'
> 
> yes and I even tried pushing for a generic netdev printk that incorporates the
> msg_enable bits properly
> 
> I also got absolutely unwelcome responses to that, if not none :)
> 
> once we get such a thing, we can incorporate this into e1000 with this patch by
> changing 2 lines. so I think this patch is still a good thing, and it certainly
> removes a lot of wrapped lines.

Jeff,

I'm not sure how to proceed with this mess cleanup so I'm removing that patch from
the series I sent, and I will revisit this issue later.

I'm resending the ones I have sent once but are on hold pending this discussion.
They are all meant for #upstream and should apply OK.

thanks,

Auke


  parent reply	other threads:[~2008-04-02 18:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 16:15 [PATCH 1/8] e1000e: reformat comment blocks, cosmetic changes only Auke Kok
2008-03-28 16:15 ` [PATCH 2/8] e1000e: rename mc_addr_list_update Auke Kok
2008-03-28 16:15 ` [PATCH 3/8] e1000e: reorganize PHY and flow control interface Auke Kok
2008-03-28 16:15 ` [PATCH 4/8] e1000e: limit EEPROM size accesses Auke Kok
2008-03-29  1:58   ` Jeff Garzik
2008-03-31 16:33     ` Kok, Auke
2008-03-28 16:15 ` [PATCH 5/8] e1000e: Make arrays out of these Rx/Tx registers Auke Kok
2008-03-28 16:15 ` [PATCH 6/8] e1000e: convert ndev_ printks to something smaller Auke Kok
2008-03-29  2:03   ` Jeff Garzik
2008-03-31 18:36     ` Kok, Auke
2008-03-31 19:09       ` Joe Perches
2008-04-02 18:55       ` Kok, Auke [this message]
2008-03-28 16:15 ` [PATCH 7/8] e1000e: rename a few functions Auke Kok
2008-03-28 16:15 ` [PATCH 8/8] e1000e: reformat register test code, fix some minor initialization Auke Kok
2008-03-29  2:16 ` [PATCH 1/8] e1000e: reformat comment blocks, cosmetic changes only Jeff Garzik

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=47F3D6B2.9070306@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    /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).