From: Amir Noam <amir.noam@intel.com>
To: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [PATCH 0/10] [bonding 2.6] port 2.4 bug fixes to 2.6
Date: Thu, 4 Sep 2003 20:43:25 +0300 [thread overview]
Message-ID: <200309042043.25567.amir.noam@intel.com> (raw)
The following set ports to 2.6 numerous bug fixes that went into
2.4 recently. Patches apply on 2.6.0-test4. Compile tested only.
patch1: fix 802.3ad long fail over with high UDP Tx stress
patch2: fix load balance problem with high UDP Tx stress
patch3: fix ARP monitoring bug
patch4: fix kernel panic when optional feature used
patch5: fix change active command
patch6: fix OOPS in bonding driver, when removing primary
patch7: embed stats struct inside bonding private struct
patch8: fix error handling in init code
patch9: make each bond device use its own /proc entry
patch10: misc fixes: missing include, typos, comments
--
Amir
next reply other threads:[~2003-09-04 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 17:43 Amir Noam [this message]
2003-09-05 8:35 ` [PATCH 0/10] [bonding 2.6] port 2.4 bug fixes to 2.6 Jeff Garzik
2003-09-11 18:55 ` 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=200309042043.25567.amir.noam@intel.com \
--to=amir.noam@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--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).