From: Shmulik Hen <shmulik.hen@intel.com>
To: <bonding-devel@lists.sourceforge.net>, <netdev@oss.sgi.com>
Subject: Re: [bonding][0/3] Synchronizing 2.4-2.6
Date: Sat, 30 Aug 2003 22:05:45 +0300 [thread overview]
Message-ID: <200308302205.45924.shmulik.hen@intel.com> (raw)
In-Reply-To: <200308271958.52063.shmulik.hen@intel.com>
On Wednesday 27 August 2003 07:58 pm, Hen, Shmulik wrote:
>
> 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
Forgot to mention free_netdev().
Is it 2.4 compatible ?
> 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 prev parent reply other threads:[~2003-08-30 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 16:58 [bonding][0/3] Synchronizing 2.4-2.6 Shmulik Hen
2003-08-30 19:05 ` Shmulik Hen [this message]
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=200308302205.45924.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.