From: Shmulik Hen <shmulik.hen@intel.com>
To: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [bonding][0/3] Synchronizing 2.4-2.6
Date: Wed, 27 Aug 2003 19:58:52 +0300 [thread overview]
Message-ID: <200308271958.52063.shmulik.hen@intel.com> (raw)
Hi,
The following 3 patch sets are meant to get bonding in 2.4 and 2.6
synchronized. I'm sending the sets again, this time diff'd against
the freshly release 2.4.22, in order to include bug fixes that we
realready accepted. The 3 sets are not independent and each one
relies on the application of the previous. Once all sets are
accepted, all bonding related files can be copied as is from 2.4 to
2.6 and get both versions to match.
o Set 1 handles back porting new stuff from 2.6 into 2.4 while fixing
some implementation bugs.
o Set 2 merges stuff from Jay Vosburgh's 5/22 experimental release
for propagating settings from the bond to its slaves with our
enhancements and fixes.
o Set 3 is a wholesale cleanup of the bonding code.
Next in store are:
o Stephen Hemminger's converting bonding driver /proc interface to
seq_file, along with changing /proc/bond0/info to
/proc/bonding/bond0
o cleanup of the 802.3ad code (was not included in this release since
it requires some code re-factoring first).
o lots of new stuff :)
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
next reply other threads:[~2003-08-27 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 16:58 Shmulik Hen [this message]
2003-08-30 19:05 ` [bonding][0/3] Synchronizing 2.4-2.6 Shmulik Hen
2003-08-30 21:27 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-08-31 10:54 Hen, Shmulik
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=200308271958.52063.shmulik.hen@intel.com \
--to=shmulik.hen@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).