From: "John W. Linville" <linville@tuxdriver.com>
To: Malli Chilakala <mallikarjuna.chilakala@intel.com>
Cc: netdev <netdev@oss.sgi.com>, "jgarzik@pobox.com" <jgarzik@pobox.com>
Subject: Re: [RESEND][PATCH net-drivers-2.6 0/16] e1000: driver update
Date: Fri, 29 Apr 2005 08:22:50 -0400 [thread overview]
Message-ID: <20050429122250.GC31796@tuxdriver.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0504281922090.29290-100000@isotope.jf.intel.com>
On Thu, Apr 28, 2005 at 07:38:17PM -0700, Malli Chilakala wrote:
> 13. 82573 specific code & packet split code
Patch 13 seems to be missing...? (2.4 version as well)
--
John W. Linville
linville@tuxdriver.com
next parent reply other threads:[~2005-04-29 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0504281922090.29290-100000@isotope.jf.intel.com>
2005-04-29 12:22 ` John W. Linville [this message]
2005-05-02 19:55 ` [RESEND][PATCH net-drivers-2.6 0/16] e1000: driver update John W. Linville
2005-04-29 2:51 Chilakala, Mallikarjuna
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=20050429122250.GC31796@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jgarzik@pobox.com \
--cc=mallikarjuna.chilakala@intel.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).