From: Jeff Garzik <jgarzik@pobox.com>
To: netdev@oss.sgi.com
Subject: [bk] 2.4.x net driver queue snapshot
Date: Tue, 26 Aug 2003 16:50:42 -0400 [thread overview]
Message-ID: <20030826205042.GA31910@gtf.org> (raw)
Here is just a snapshot of my 2.4 net driver queue. Marcelo pulled
yesterday, including some bonding bits. No GNU patch for snapshots, as
the queue is still being grown...
BK users:
bk pull bk://kernel.bkbits.net/jgarzik/net-drivers-2.4
or
bk pull http://gkernel.bkbits.net/net-drivers-2.4
This will update the following files:
drivers/net/3c501.c | 93 ++--------
drivers/net/3c503.c | 71 +------
drivers/net/3c505.c | 92 +--------
drivers/net/3c507.c | 97 ++--------
drivers/net/3c515.c | 94 ++--------
drivers/net/3c523.c | 73 +------
drivers/net/3c527.c | 94 ++--------
drivers/net/3c59x.c | 50 ++---
drivers/net/8139cp.c | 472 ++++++++++++++++++++-------------------------------
drivers/net/dmfe.c | 61 +-----
drivers/net/sis900.c | 53 ++---
11 files changed, 362 insertions(+), 888 deletions(-)
through these ChangeSets:
<jgarzik@redhat.com> (03/08/26 1.1085)
[netdrvr] ethtool_ops support for 3c515, 3c523, 3c527, and dmfe
<jgarzik@redhat.com> (03/08/26 1.1084)
[netdrvr] ethtool_ops support in 3c503, 3c505, 3c507
<jgarzik@redhat.com> (03/08/26 1.1083)
[netdrvr 3c501] ethtool_ops support
<jgarzik@redhat.com> (03/08/26 1.1082)
[netdrvr 3c59x] add a piece missed in previous ethtool_ops patch
Contributed by Matthew Wilcox.
<jgarzik@redhat.com> (03/08/26 1.1081)
[netdrvr 8139cp] ethtool_ops support
<jgarzik@redhat.com> (03/08/26 1.1080)
[netdrvr 8139cp] minor bits from 2.6
<jgarzik@redhat.com> (03/08/26 1.1079)
[netdrvr sis900] minor bits from 2.6
<jgarzik@redhat.com> (03/08/26 1.1078)
[netdrvr sis900] ethtool_ops support
<willy@debian.org> (03/08/26 1.1077)
[netdrvr 3c59x] ethtool_ops support
reply other threads:[~2003-08-26 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030826205042.GA31910@gtf.org \
--to=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).