From: Joe Perches <joe@perches.com>
To: Jim Keniston <jkenisto@us.ibm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Net device error logging
Date: Thu, 02 Oct 2003 17:36:17 -0700 [thread overview]
Message-ID: <1065141377.6667.27.camel@localhost.localdomain> (raw)
In-Reply-To: <3F7C967F.A06A512E@us.ibm.com>
On Thu, 2003-10-02 at 14:19, Jim Keniston wrote:
> The enclosed patch, updated for v2.6.0-test6, implements the previously
> discussed netdev_* error-logging macros for network drivers. Please apply.
While I agree with the completely with the concept and nearly completely
with the implementation, can I suggest that this should be done in the
2.7 series?
next prev parent reply other threads:[~2003-10-03 0:36 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 [this message]
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
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=1065141377.6667.27.camel@localhost.localdomain \
--to=joe@perches.com \
--cc=jgarzik@pobox.com \
--cc=jkenisto@us.ibm.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