From: Shmulik Hen <shmulik.hen@intel.com>
To: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [SET 1][PATCH 0/6][bonding] backport 2.6 changes to 2.4
Date: Fri, 8 Aug 2003 17:44:09 +0300 [thread overview]
Message-ID: <200308081744.09189.shmulik.hen@intel.com> (raw)
Hi,
I'm resending Amir's patch set, this time diff'd against
2.4.22-rc1 to include all the bug fixes accepted into 2.4, and
with some version/comments fixes.
This set backports changes done on bonding in 2.6 while
fixing some bugs. Once this set is fully merged into 2.4, all
bonding files may be copied as-is into 2.6 and get both in sync.
1 - Add list_for_each_entry_safe()
2 - Export alloc_netdev()
3 - Fix /proc read function
4 - Put the bond's net_device_stats inside the bond struct
5 - Use a linked list to handle multiple bond devices
6 - Update versions/contributions in header and bump version
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
reply other threads:[~2003-08-08 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308081744.09189.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).