From: Nivedita Singhvi <niv@us.ibm.com>
To: Janice M Girouard <janiceg@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
stekloff@us.ibm.com, girouard@us.ibm.com, lkessler@us.ibm.com,
kenistonj@us.ibm.com, Jeff Garzik <jgarzik@pobox.com>,
davem@redhat.com
Subject: Re: patch for common networking error messages
Date: Mon, 16 Jun 2003 15:13:05 -0700 [thread overview]
Message-ID: <3EEE40F1.4030107@us.ibm.com> (raw)
In-Reply-To: <3EEE28DE.6040808@us.ibm.com>
Janice M Girouard wrote:
> Below is a patch that demonstrates standard messages for ethernet device
> drivers. I would like your feedback on the concept of standard network
> messages, and any suggestions for messages to include.
Very useful! I'd like to see a short note on this in Documentation/
networking..Or perhaps if there is already a RAS best practices
kind of doc or something, add to that? (sorry, havent checked)
But it would be handy for people who wanted to contribute
patches for other drivers.
Essentially, things like some guidelines on classifying some
of those messages, when creating new messages. eg when is
something a state change and when is it a performance event?
I notice some slight ambiguity in your defs..(sorry, very
minor nitpick :)).
I'd certainly like to see messages from the driver when the
card enters/leaves promiscuous mode, as an example of things
we'd like to add...
thanks,
Nivedita
> The intent of the standard message change is to:
> 1) Ensure key events are communicated to user space in a predictable
> way, enabling automated diagnostic systems or error log analysis,
> 2) Reduce the number of puzzling messages that are logged -- in this
> case, by replacing them with standard messages, and/or
> 3) Identify the device (or driver name) that is responsible for the error.
next prev parent reply other threads:[~2003-06-16 22:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 20:30 patch for common networking error messages Janice M Girouard
2003-06-16 20:38 ` David S. Miller
2003-06-16 20:53 ` Andi Kleen
2003-06-16 20:51 ` David S. Miller
2003-06-16 22:27 ` Andrew Morton
2003-06-17 7:09 ` Andi Kleen
2003-06-17 7:20 ` Andrew Morton
2003-06-16 20:59 ` Janice M Girouard
2003-06-16 22:48 ` Jeff Garzik
2003-06-16 22:52 ` Jeff Garzik
2003-06-16 22:13 ` Nivedita Singhvi [this message]
2003-06-16 22:13 ` David S. Miller
2003-06-16 22:50 ` Nivedita Singhvi
2003-06-16 22:57 ` David S. Miller
2003-06-16 23:02 ` Donald Becker
-- strict thread matches above, loose matches on Subject: below --
2003-06-16 22:29 Janice Girouard
2003-06-16 22:27 ` David S. Miller
2003-06-16 22:45 ` Nivedita Singhvi
2003-06-16 22:52 ` David S. Miller
2003-06-17 0:07 ` Nivedita Singhvi
2003-06-16 22:50 Janice Girouard
2003-06-16 22:55 ` David S. Miller
2003-06-21 12:36 ` Alan Cox
2003-06-21 14:27 ` Jamal Hadi
2003-06-23 0:46 ` David S. Miller
2003-06-23 11:54 ` Alan Cox
2003-06-17 0:44 Janice Girouard
2003-06-17 1:19 ` David S. Miller
2003-06-17 14:34 ` Mr. James W. Laferriere
2003-06-17 2:12 Janice Girouard
2003-06-17 4:34 ` Valdis.Kletnieks
2003-06-17 16:08 ` Stephen Hemminger
2003-06-17 16:09 ` David S. Miller
2003-06-17 18:46 ` Jeff Garzik
2003-06-17 19:06 ` Janice M Girouard
2003-06-17 19:23 ` Jeff Garzik
2003-06-17 19:46 ` Janice M Girouard
2003-06-17 19:50 ` David S. Miller
2003-06-17 20:24 ` Janice M Girouard
2003-06-17 20:27 ` David S. Miller
2003-06-17 20:40 Janice Girouard
2003-06-17 20:42 ` David S. Miller
2003-06-17 20:57 Janice Girouard
2003-06-17 21:14 ` David S. Miller
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=3EEE40F1.4030107@us.ibm.com \
--to=niv@us.ibm.com \
--cc=davem@redhat.com \
--cc=girouard@us.ibm.com \
--cc=janiceg@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=kenistonj@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkessler@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=stekloff@us.ibm.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).