From: Jeff Garzik <jgarzik@pobox.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: [BK PATCHES] net driver merges
Date: Thu, 29 May 2003 17:10:53 -0400 [thread overview]
Message-ID: <20030529211053.GA9069@gtf.org> (raw)
Linus, please do a
bk pull bk://kernel.bkbits.net/jgarzik/net-drivers-2.5
Others may download the patch from
ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.5/2.5.70-bk3-netdrvr1.patch.bz2
This will update the following files:
drivers/net/8139too.c | 6
drivers/net/amd8111e.c | 1047 +++++++++++++++++++++++++++----------------
drivers/net/amd8111e.h | 968 ++++++++++++++++++++-------------------
drivers/net/e100/e100_main.c | 33 -
drivers/net/pci-skeleton.c | 4
drivers/net/pcnet32.c | 7
drivers/net/r8169.c | 44 +
drivers/net/tlan.c | 116 +++-
8 files changed, 1306 insertions(+), 919 deletions(-)
through these ChangeSets:
<shemminger@osdl.org> (03/05/29 1.1438)
[netdrvr e100] initialize callbacks before registering netdev
Ouch.
<reeja.john@amd.com> (03/05/29 1.1437)
[netdrvr amd8111e] interrupt coalescing, libmii, bug fixes
* Dynamic interrupt coalescing
* mii lib support
* dynamic IPG support (disabled by default)
* jumbo frame fix
* vlan fix
* rx irq coalescing fix
<alan@lxorguk.ukuu.org.uk> (03/05/29 1.1436)
[netdrvr tlan] fix 64-bit issues
<jgarzik@redhat.com> (03/05/29 1.1435)
[netdrvr r8169] use alloc_etherdev, pci_disable_device
<jgarzik@redhat.com> (03/05/29 1.1433)
[netdrvr 8139too] respond to "isn't this racy?" comment
<jgarzik@redhat.com> (03/05/28 1.1432)
[netdrvr] s/init_etherdev/alloc_etherdev/ in code comments,
in 8139too and pci-skeleton drivers.
<jgarzik@redhat.com> (03/05/28 1.1431)
[netdrvr tlan] cleanup
* use pci_{request,release}_regions for PCI devices
* use alloc_etherdev (fixes race)
* propagate error returns from pci_xxx function errors
<engebret@us.ibm.com> (03/05/27 1.1392.7.7)
[netdrvr pcnet32] bug fixes
I would like to see a couple of the pcnet32 changes that I think we can
agree on be put into the trees so a couple of the potential defects can be
avoided. The following patch contains just these pieces. The only
controversial one is an arbitrary change in the number of iterations in a
while loop spinning on hardware state. No matter how this is done, I am
not especially fond of this bit of code as it has no reasonable error
recovery path -- however, as a half-way, incremental solution, increasing
the polling time should help as the 100 value was certainly found to be
insufficient. 1000 may not be sufficient either, but it is certainly no
worse.
Both of the other changes were hit in testing (and I belive the wmb() at a
customer even), so it would help reduce some debug if these go in. Any
feedback is appreciated - thanks.
next reply other threads:[~2003-05-29 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 21:10 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-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-03-22 22:27 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=20030529211053.GA9069@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--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;
as well as URLs for NNTP newsgroup(s).