From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
linux-kernel@vger.kernel.org, Joshua Hudson <joshudson@gmail.com>
Subject: Re: [GIT PATCH] Remove devfs from 2.6.17
Date: Mon, 19 Jun 2006 15:17:51 -0700 [thread overview]
Message-ID: <4497228F.9030108@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606191801000.6713@iabervon.org>
Daniel Barkalow wrote:
> On Mon, 19 Jun 2006, Alexander E. Patrakov wrote:
>
>> Will Dyson wrote:
>>> Providing the information about what devices a virtual driver will
>>> register when loaded seems like a good idea.
>> Why? This information is currently useless. What you want is that something
>> knows that you want this driver to be loaded.
>
> The point is that you *don't* want those modules to be loaded. What you
> want is for the kernel to know that those modules are available, and
> therefore mention that drivers could be found for those devices, and
> therefore udev would create the device nodes for them, even though the
> kernel doesn't contain a module that drives them yet.
>
The kernel doesn't need to know. udev needs to know.
-hpa
next prev parent reply other threads:[~2006-06-19 22:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 22:13 [GIT PATCH] Remove devfs from 2.6.17 Greg KH
2006-06-18 22:45 ` Michal Piotrowski
2006-06-18 23:06 ` Greg KH
2006-06-18 23:00 ` Samuel Thibault
2006-06-18 23:12 ` Greg KH
2006-06-18 23:35 ` Samuel Thibault
2006-06-19 0:48 ` Nick Piggin
2006-06-19 3:22 ` Greg KH
2006-06-19 8:23 ` Samuel Thibault
2006-06-19 9:30 ` Marcel Holtmann
2006-06-19 9:39 ` Samuel Thibault
2006-06-19 10:22 ` Marcel Holtmann
2006-06-19 0:54 ` H. Peter Anvin
2006-06-19 1:17 ` Joshua Hudson
2006-06-19 1:35 ` H. Peter Anvin
2006-06-19 5:55 ` Will Dyson
2006-06-19 7:14 ` Alexander E. Patrakov
2006-06-19 22:14 ` Daniel Barkalow
2006-06-19 22:17 ` H. Peter Anvin [this message]
2006-06-19 3:15 ` Greg KH
2006-06-19 8:52 ` Samuel Thibault
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=4497228F.9030108@zytor.com \
--to=hpa@zytor.com \
--cc=barkalow@iabervon.org \
--cc=joshudson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
/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