From: "David S. Miller" <davem@redhat.com>
To: "Chad N. Tindel" <chad@tindel.net>
Cc: fubar@us.ibm.com, shmulik.hen@intel.com, jgarzik@pobox.com,
chad@tindel.net, bonding-devel@lists.sourceforge.net,
netdev@oss.sgi.com
Subject: Re: [Bonding-devel] Re: [bonding] compatibilty issues
Date: Wed, 1 Oct 2003 00:05:24 -0700 [thread overview]
Message-ID: <20031001000524.7e0d851e.davem@redhat.com> (raw)
In-Reply-To: <20030930213650.GA71877@calma.pair.com>
On Tue, 30 Sep 2003 17:36:50 -0400
"Chad N. Tindel" <chad@tindel.net> wrote:
> My recommendations are more towards the middle than either end. I would
> like to see us get rid of the _OLD ioctls in the 2.6 kernel specifically
> because it uses the SIOCDEVPRIVATE ioctls.
...
> I would like to see them stay in 2.4 for the rest of the 2.4 tree
> specifically so that people who want to run on 3 year old systems
> can continue to do so without us breaking their world.
I think this is fine, personally.
I defer to Jeff for final judgment, he should be allowed to chime in
at least once more.
next prev parent reply other threads:[~2003-10-01 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464F1@hasmsx403.iil.intel.com>
2003-09-30 11:42 ` [bonding] compatibilty issues Shmulik Hen
2003-09-30 16:39 ` [Bonding-devel] " Jay Vosburgh
2003-09-30 21:36 ` Chad N. Tindel
2003-10-01 7:05 ` David S. Miller [this message]
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464F2@hasmsx403.iil.intel.com>
2003-10-01 8:49 ` Shmulik Hen
2003-10-01 18:26 ` Chad N. Tindel
2003-10-01 19:25 ` Jay Vosburgh
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464F9@hasmsx403.iil.intel.com>
2003-10-02 6:37 ` Shmulik Hen
2003-10-03 19:57 ` Jay Vosburgh
2003-10-02 7:57 ` Shmulik Hen
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=20031001000524.7e0d851e.davem@redhat.com \
--to=davem@redhat.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=chad@tindel.net \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--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).