From: Tom Rini <trini@kernel.crashing.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18pre24
Date: Thu, 30 Nov 2000 11:26:43 -0700 [thread overview]
Message-ID: <20001130112643.A16256@opus.bloom.county> (raw)
In-Reply-To: <E140wh7-0005Na-00@the-village.bc.nu> <20001129150159.Y872@opus.bloom.county> <20001130181740.A18566@athlon.random>
In-Reply-To: <20001130181740.A18566@athlon.random>; from andrea@suse.de on Thu, Nov 30, 2000 at 06:17:40PM +0100
On Thu, Nov 30, 2000 at 06:17:40PM +0100, Andrea Arcangeli wrote:
> On Wed, Nov 29, 2000 at 03:01:59PM -0700, Tom Rini wrote:
> > As Dave Miller pointed out, DEV_MAC_HID sysctl conflicts with the RAID patches
>
> That's right but OTOH I'd simply declare the sysctl-by-number interface dead
> for new introduced sysctl. We need to preserve backwards compatibility of
> course but that's not a problem. I'd preferred if we killed it completly (just
> providing backwards compatibility) during the 2.4.x cycle. Only reliable
> way to use new sysctl is sysctl-by-name IMHO.
Right. But the problem here was a new, unused sysctl-by-number, conflicted
with an old-but-not-integrated sysctl-by-number that is used. :) The only
reason I made the number match the one in 2.4 was because a) i figured it's
not going to conflict. :) and b) incase something does come along and use it.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 2:09 Linux 2.2.18pre24 Alan Cox
2000-11-29 22:01 ` Tom Rini
2000-11-30 17:17 ` Andrea Arcangeli
2000-11-30 18:26 ` Tom Rini [this message]
2000-11-30 19:35 ` Andrea Arcangeli
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=20001130112643.A16256@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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