archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <>
Subject: [BK PATCHES] net driver merges
Date: Tue, 27 May 2003 01:55:05 -0400	[thread overview]
Message-ID: <> (raw)

Linus, please do a

	bk pull bk://

Others may download the patch from

This will update the following files:

 drivers/net/bonding/bond_3ad.c  |   95 ++++++++++++---------
 drivers/net/bonding/bond_main.c |   12 ++
 drivers/net/eepro.c             |    2 
 drivers/net/pcnet32.c           |    7 +
 drivers/net/sundance.c          |   33 +++++--
 drivers/net/wan/lmc/lmc_debug.c |    2 
 drivers/net/wan/lmc/lmc_main.c  |  174 +++++++++-------------------------------
 drivers/net/wan/lmc/lmc_media.c |    7 -
 drivers/net/wan/lmc/lmc_proto.c |   14 ---
 drivers/net/wan/lmc/lmc_var.h   |    9 --
 10 files changed, 137 insertions(+), 218 deletions(-)

through these ChangeSets:

<> (03/05/27 1.1436)
   [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
   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.

<> (03/05/27 1.1435)
   [netdrvr eepro] update MODULE_AUTHOR per old-author request

<> (03/05/27 1.1434)
   [netdrvr sundance] fix another flow control bug

<> (03/05/27 1.1433)
   [netdrvr sundance] fix flow control bug

<> (03/05/27 1.1432)
   [wan lmc] remove 2.0.x-era code
   The patch below removes obsolete #if'd code for kernel 2.0 and 2.2 from
   drivers/net/wan/lmc/* (this includes the expansion of some #define's 
   that were definded differently for different kernel versions).

<> (03/05/27 1.1431)
   [netdrvr bonding] fix ABI version control problem
   This fix makes bonding not commit to a specific ABI version if the ioctl
   command is not supported by bonding.
   (It also removes the '\n' in the continuous printk reporting the link down
   event in bond_mii_monitor - it got in there by mistake in our previous
   patch set and caused log messages to appear funny in some situations).

<> (03/05/27 1.1430)
   [netdrvr bonding] fix long failover in 802.3ad mode
   This patch fixes the bug reported by Jay on April 3rd regarding long
   failover time when releasing the last slave in the active aggregator. The
   fix, as suggested by Jay, is to follow the spec recommendation and send a
   LACPDU to the partner saying this port is no longer aggregatable and
   therefore trigger an immediate re-selection of a new aggregator instead of
   waiting the entire expiration timeout.

             reply	other threads:[~2003-05-27  5:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  5:55 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-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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).