public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: "David S. Miller" <davem@redhat.com>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18pre21
Date: Fri, 10 Nov 2000 08:42:11 -0700	[thread overview]
Message-ID: <20001110084211.B24101@opus.bloom.county> (raw)
In-Reply-To: <200011100344.TAA01282@pizda.ninka.net> <19341005050711.11931@192.168.1.2>
In-Reply-To: <19341005050711.11931@192.168.1.2>; from bh40@calva.net on Fri, Nov 10, 2000 at 12:35:27PM +0100

On Fri, Nov 10, 2000 at 12:35:27PM +0100, Benjamin Herrenschmidt wrote:
> >   o	Resnchronize Apple PowerMac codebase		(Paul Mackerras & co)
> >
> >BUUUG, new DEV_MAC_HID sysctl number conflicts with DEV_MD
> >in Ingo's raid patches.
> 
> Well, I beleive DEV_MAC_HID can safely be changed to something else as
> userland only use the /proc entry name./

One question here.  Is it important here that the # be consistant?  I mean
since to change a sysctl isn't the name the important bit? ie:
dev.md.speed_limit would work regardless of if DEV_MD is 3 or 4?

-- 
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/

  reply	other threads:[~2000-11-10 15:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10  3:07 Linux 2.2.18pre21 Alan Cox
2000-11-10  3:44 ` David S. Miller
2000-11-10 11:35   ` Benjamin Herrenschmidt
2000-11-10 15:42     ` Tom Rini [this message]
2000-11-10 15:34       ` David S. Miller
2000-11-10 10:59 ` Arnaud S . Launay
2000-11-10 10:52   ` David S. Miller
2000-11-16 14:07 ` Matthias Andree
2000-11-16 16:16   ` Andrea Arcangeli
2000-11-16 19:52     ` jesse
2000-11-16 20:02       ` chroot [Was: Re: Linux 2.2.18pre21] Kurt Roeckx
2000-11-16 21:40       ` Linux 2.2.18pre21 Alan Cox
2000-11-18 10:07         ` Rogier Wolff
2000-11-18 17:32           ` kuznet
2000-11-18 17:34             ` Rogier Wolff
2000-11-18 17:47               ` kuznet
2000-11-18 17:51                 ` Rogier Wolff
2000-11-16 22:56       ` Matthias Andree
2000-11-17  6:30       ` Peter Samuelson
2000-11-17  6:40         ` H. Peter Anvin
2000-11-17 11:22           ` Peter Samuelson
2000-11-17 17:35             ` H. Peter Anvin
2000-11-17 11:34           ` Matthias Andree
2000-11-17 19:23         ` jesse
2000-11-18 20:44           ` Pavel Machek
2000-11-18  1:38         ` Nix
2000-11-21  4:19           ` Peter Samuelson
  -- strict thread matches above, loose matches on Subject: below --
2000-11-10  9:28 willy tarreau
2000-11-10  9:44 ` Matti Aarnio
2000-11-10  9:57   ` Constantine Gavrilov
2000-11-10 10:14     ` Matti Aarnio
2000-11-10 10:22       ` Constantine Gavrilov
2000-11-10 10:51         ` Matti Aarnio
2000-11-10 19:11           ` Thomas Davis
2000-11-10 10:18 ` Constantine Gavrilov
2000-11-10 10:40 willy tarreau
2000-11-10 10:49 willy tarreau
2000-11-10 11:21 willy tarreau
2000-11-13  7:00 willy tarreau
2000-11-13  9:47 willy tarreau

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=20001110084211.B24101@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bh40@calva.net \
    --cc=davem@redhat.com \
    --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