From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [BK PATCHES] net driver merges
Date: Sat, 22 Mar 2003 17:27:02 -0500 [thread overview]
Message-ID: <3E7CE336.4060503@pobox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 71 bytes --]
Just some small bits that should have been in the last batch.
Jeff
[-- Attachment #2: net-drivers-2.5.txt --]
[-- Type: text/plain, Size: 635 bytes --]
Linus, please do a
bk pull bk://kernel.bkbits.net/jgarzik/net-drivers-2.5
This will update the following files:
MAINTAINERS | 5 +++++
drivers/net/e1000/e1000_param.c | 4 ++--
2 files changed, 7 insertions(+), 2 deletions(-)
through these ChangeSets:
<jgarzik@redhat.com> (03/03/22 1.1201)
[via-rhine] note that Roger is maintainer, in MAINTAINERS
<scott.feldman@intel.com> (03/03/22 1.1200)
[E1000] Increase default Rx descriptors to 256
* Increase default Rx descriptors from 80 to 256 to give
better Rx buffering capability in the case of heavy
Rx load with small packets.
next reply other threads:[~2003-03-22 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 22:27 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-08 23:26 [BK PATCHES] net driver merges Jeff Garzik
2003-06-24 2:32 Jeff Garzik
2003-06-20 3:46 Jeff Garzik
2003-06-06 5:42 Jeff Garzik
2003-05-29 21:10 Jeff Garzik
2003-05-27 5:55 Jeff Garzik
2003-05-26 0:26 Jeff Garzik
2003-05-11 18:36 [BK+PATCHES] " Jeff Garzik
2003-04-28 4:55 [BK PATCHES] " Jeff Garzik
2003-04-28 7:22 ` Aaron Lehmann
2003-04-28 13:40 ` Jeff Garzik
2003-04-26 4:17 Jeff Garzik
2003-03-29 5:46 Jeff Garzik
2003-01-04 0:02 Jeff Garzik
2003-01-04 1:27 ` Jeff Garzik
2002-02-09 0:25 Jeff Garzik
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=3E7CE336.4060503@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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