From: "John W. Linville" <linville@tuxdriver.com>
To: akpm@osdl.org
Cc: davem@davemloft.net, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [patch 04/13] e100: NAPI fixes
Date: Tue, 15 Mar 2005 18:16:34 -0500 [thread overview]
Message-ID: <20050315231632.GA18393@tuxdriver.com> (raw)
In-Reply-To: <200503152222.j2FMMawn016802@shell0.pdx.osdl.net>
On Tue, Mar 15, 2005 at 02:22:41PM -0800, akpm@osdl.org wrote:
>
> From: "John W. Linville" <linville@tuxdriver.com>
>
> Just curious...wanna try this patch I got from Intel? I think it
> may help...
Hmmm...I didn't really mean for that one to be a submission...
Hopefully the Intel e100 guys will be covering this in one of their
updates (if they haven't already)...
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2005-03-15 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 22:22 [patch 04/13] e100: NAPI fixes akpm
2005-03-15 23:16 ` John W. Linville [this message]
2005-03-15 23:23 ` Andrew Morton
2005-03-16 15:45 ` John W. Linville
2005-03-16 15:51 ` [patch 2.6.11] e100: NAPI state machine fix John W. Linville
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=20050315231632.GA18393@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).