From: "David S. Miller" <davem@redhat.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: netdev@oss.sgi.com, janitor@sternwelten.at
Subject: Re: Fw: [Kernel-janitors] old ioctl definitions in 2.5
Date: Mon, 15 Sep 2003 15:54:15 -0700 [thread overview]
Message-ID: <20030915155415.73c5056d.davem@redhat.com> (raw)
In-Reply-To: <20030915155225.3cf90d79.rddunlap@osdl.org>
On Mon, 15 Sep 2003 15:52:25 -0700
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
> I think that we need to ask the netdev people about this...
If the current generation of the bonding userland tools
have stopped using these older ioctl values, yes we should
kill them from the entire kernel tree.
next prev parent reply other threads:[~2003-09-15 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 22:52 Fw: [Kernel-janitors] old ioctl definitions in 2.5 Randy.Dunlap
2003-09-15 22:54 ` David S. Miller [this message]
2003-09-15 23:57 ` Jay Vosburgh
2003-09-15 23:53 ` David S. Miller
2003-09-16 1:11 ` Jay Vosburgh
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464A9@hasmsx403.iil.intel.com>
2003-09-16 13:31 ` Shmulik Hen
2003-09-16 17:33 ` Jay Vosburgh
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=20030915155415.73c5056d.davem@redhat.com \
--to=davem@redhat.com \
--cc=janitor@sternwelten.at \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.org \
/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).