From: Jeff Garzik <jgarzik@pobox.com>
To: shmulik.hen@intel.com
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [bonding][0/3] Synchronizing 2.4-2.6
Date: Sat, 30 Aug 2003 17:27:25 -0400 [thread overview]
Message-ID: <3F5116BD.9030601@pobox.com> (raw)
In-Reply-To: <200308302205.45924.shmulik.hen@intel.com>
Shmulik Hen wrote:
> 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 ?
Only if you create a patch for 2.4 :)
Jeff
next prev parent reply other threads:[~2003-08-30 21:27 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
2003-08-30 21:27 ` Jeff Garzik [this message]
-- 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=3F5116BD.9030601@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@intel.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).