From: Jay Vosburgh <fubar@us.ibm.com>
To: shmulik.hen@intel.com
Cc: "David S. Miller" <davem@redhat.com>,
rddunlap@osdl.org, netdev@oss.sgi.com, janitor@sternwelten.at
Subject: Re: Fw: [Kernel-janitors] old ioctl definitions in 2.5
Date: Tue, 16 Sep 2003 10:33:39 -0700 [thread overview]
Message-ID: <200309161733.h8GHXdTJ013890@death.ibm.com> (raw)
In-Reply-To: Message from Shmulik Hen <shmulik.hen@intel.com> of "Tue, 16 Sep 2003 16:31:48 +0300." <200309161631.48653.shmulik.hen@intel.com>
>On Tuesday 16 September 2003 04:11 am, Jay Vosburgh wrote:
>> >On Mon, 15 Sep 2003 16:57:26 -0700
>> >
>> >Jay Vosburgh <fubar@us.ibm.com> wrote:
>> >> My only concern is a matter of timing; we're right at the
>> >> end of synchronizing the 2.4 and 2.6 bonding sources. Once
>> >> that's settled (hopefully in a few days, the last patch set for
>> >> 2.4 came in this morning), then removing them from that header
>> >> and the bonding code should be fine.
>> >
>> >No problem. Just push the change to Jeff then after you're
>> >done merging stuff around, ok?
>>
>> Will do.
>
>I'm on the verge of finishing my cleanup set re-do. Now that Amir sent
>all the synching stuff, I could put that one in as well, and it would
>fit on both 2.4 and 2.6.
I was going to add it on to the end of the clean up set, but
if you want to do it, go ahead. Nobody seems to have objected to
removing the _OLD stuff, which I view as a good thing.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2003-09-16 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464A9@hasmsx403.iil.intel.com>
2003-09-16 13:31 ` Fw: [Kernel-janitors] old ioctl definitions in 2.5 Shmulik Hen
2003-09-16 17:33 ` Jay Vosburgh [this message]
2003-09-15 22:52 Randy.Dunlap
2003-09-15 22:54 ` David S. Miller
2003-09-15 23:57 ` Jay Vosburgh
2003-09-15 23:53 ` David S. Miller
2003-09-16 1:11 ` 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=200309161733.h8GHXdTJ013890@death.ibm.com \
--to=fubar@us.ibm.com \
--cc=davem@redhat.com \
--cc=janitor@sternwelten.at \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.org \
--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).