From: Jeff Garzik <jgarzik@pobox.com>
To: marcelo@parcelfarce.linux.theplanet.co.uk
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: [bk patches] 2.4.x net driver updates
Date: Mon, 1 Sep 2003 11:49:45 -0400 [thread overview]
Message-ID: <20030901154945.GA22275@gtf.org> (raw)
Marcelo, please do a
bk pull bk://kernel.bkbits.net/jgarzik/net-drivers-2.4
This will update the following files:
drivers/net/8139cp.c | 35 ++++++++-----------------
drivers/net/8139too.c | 68 ++++++++++++++++++++++++--------------------------
2 files changed, 44 insertions(+), 59 deletions(-)
through these ChangeSets:
<jgarzik@redhat.com> (03/08/31 1.1119)
[netdrvr 8139cp] PCI MWI cleanup; remove unneeded workaround
* The PCI layer now handles incorrect cacheline size settings,
as it should. Remove our own workarounds.
* Move pci_set_mwi up much earlier in the probe process,
and check its return value.
* Call pci_clear_mwi() in ->probe error handling
* Call pci_clear_mwi() in ->remove
<hirofumi@mail.parknet.co.jp> (03/08/31 1.1117)
[netdrvr 8139too] don't start thread when it's not needed
The thread for was unneeded on chips other than CH_8139_K/8129. So,
this patch doesn't create the thread on chips other than
CH_8139_K/8129.
<hirofumi@mail.parknet.co.jp> (03/08/31 1.1116)
[netdrvr 8139too] remove driver-based poisoning of net_device
Harmless in 2.4, but causes oopses on rmmod in 2.6.
slab poisoning can take care of this for us, anyway.
<jgarzik@redhat.com> (03/08/31 1.1115)
[netdrvr 8139cp] must call NAPI-specific vlan hook
next reply other threads:[~2003-09-01 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 15:49 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 21:17 [BK PATCHES] 2.4.x net driver updates Jeff Garzik
2005-03-04 0:33 Jeff Garzik
2004-08-29 0:26 Jeff Garzik
2003-10-14 19:01 Jeff Garzik
2003-08-31 14:09 [bk patches] " Jeff Garzik
2003-08-08 0:59 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=20030901154945.GA22275@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=marcelo@parcelfarce.linux.theplanet.co.uk \
--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).