public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Kessler <kessler@us.ibm.com>
To: Jim Keniston <jkenisto@us.ibm.com>, Joe Perches <joe@perches.com>
Cc: acme@conectiva.com.br, Jeff Garzik <jgarzik@pobox.com>,
	Andrew Morton <akpm@osdl.org>, jkenisto <jkenisto@us.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Net device error logging
Date: Tue, 7 Oct 2003 14:58:30 -0700	[thread overview]
Message-ID: <200310071458.30548.kessler@us.ibm.com> (raw)
In-Reply-To: <3F8314A9.6FDD0274@us.ibm.com>

On Tuesday 07 October 2003 12:31, Jim Keniston wrote:
> 1. Is __netdev_printk's message-prefix format the right one?  If not,
> what should it be?

IMO, yes its the right format, since it identifies which device, and in a
consistent way similar to dev_printk().  What's more important than re-opening
this debate is making the current version available in the base so drivers can
start being modified to use it.  The message-prefix could change, if
experience indicates a benefit for consumers of printk messages.  

> 2. Should we support some sort of configurable prefix format?  E.g.,
> In my driver, I want the prefix to give the driver name, interface
> name, and source file and line number, so...
> 	netdev->msg_prefix = "%D:%I: %F:%L: ";
 
There are cases where a configurable prefix makes sense, but the goal here for
netdev_printk() was clearly stated from the beginning (id which device...no more, 
no less).  

> 3. Should netdev_* instead be used to enforce the "right" format?

Yes, for reasons already stated.

      reply	other threads:[~2003-10-07 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02 21:19 [PATCH] Net device error logging Jim Keniston
2003-10-02 22:05 ` acme
2003-10-03  0:36 ` Joe Perches
2003-10-06 23:52   ` Jim Keniston
     [not found]     ` <1065491087.2601.103.camel@localhost.localdomain>
2003-10-07 19:31       ` Jim Keniston
2003-10-07 21:58         ` Larry Kessler [this message]

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=200310071458.30548.kessler@us.ibm.com \
    --to=kessler@us.ibm.com \
    --cc=acme@conectiva.com.br \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=jkenisto@us.ibm.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@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