From: Jesper Juhl <jesper.juhl@gmail.com>
To: gcoady@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6..15-rc7: CONFIG_HOTPLUG help text
Date: Fri, 30 Dec 2005 00:35:59 +0100 [thread overview]
Message-ID: <9a8748490512291535i3b58b99ex80e3e45d7ebeac22@mail.gmail.com> (raw)
In-Reply-To: <0as8r1dh78udset3vv3d1sea5lpnkqccoi@4ax.com>
On 12/30/05, Grant Coady <grant_lkml@dodo.com.au> wrote:
> On Fri, 30 Dec 2005 00:19:03 +0100, Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
> >On 12/30/05, Grant Coady <grant_lkml@dodo.com.au> wrote:
> >> Hi there,
> >>
> >> "
> >> CONFIG_HOTPLUG:
> >>
> >> This option is provided for the case where no in-kernel-tree
> >> modules require HOTPLUG functionality, but a module built
> >> outside the kernel tree does. Such modules require Y here.
> >> "
> >>
> >> This gives no indication it is required for udev. Or is it me confused?
> >>
> >It doesn't mention udev specifically, but it does say quite clearly
> >that it's for out-of-kernel stuff that requires hotplug, and udev is
> >such a thing.
>
> udev is an out-of-tree kernel module? Okay, why not bring it into
> the mainline kernel then? ;)
>
Heh, ok, you are right, I guess my eyes skipped the "module" bit. I
guess it should say something along the lines of
This option is provided for the case where no in-kernel-tree
modules require HOTPLUG functionality, but a module (or
other piece of software, like udev) built outside the kernel
tree does.
Such modules and other out-of-tree software require Y here.
If in doubt say Y.
How's that for a better wording?
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-12-29 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 23:07 Grant Coady
2005-12-29 23:19 ` Jesper Juhl
2005-12-29 23:30 ` Grant Coady
2005-12-29 23:35 ` Jesper Juhl [this message]
2005-12-29 23:50 ` Grant Coady
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=9a8748490512291535i3b58b99ex80e3e45d7ebeac22@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=gcoady@gmail.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
all inboxes | Powered by JetHome®