From: Rob Love <rml@ximian.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] add sysfs mem device support [2/4]
Date: Tue, 23 Dec 2003 11:07:45 -0500 [thread overview]
Message-ID: <1072195665.3472.13.camel@fur> (raw)
In-Reply-To: <1072193516.3472.3.camel@fur>
On Tue, 2003-12-23 at 10:31, Rob Love wrote:
> Creating them via udev is the point.
>
> Remember, the ultimate goal is to have udev in initramfs during early
> boot, and all of these vital devices will be created.
>
> For udev to work as intended, all devices on the system must be
> represented in sysfs.
Oh, I think I get your point, now.
The devices actually do not need to be in sysfs, but we do need to
generate a hotplug event for them.
Nonetheless, I think it makes sense to also put them in sysfs. I think
of sysfs has a "device tree" and not necessarily a "physical device
tree".
Rob Love
next prev parent reply other threads:[~2003-12-23 16:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:21 [PATCH] some sysfs patches for 2.6.0 [0/4] Greg KH
2003-12-23 0:24 ` [PATCH] fix sysfs oops [1/4] Greg KH
2003-12-23 0:26 ` [PATCH] add sysfs mem device support [2/4] Greg KH
2003-12-23 0:28 ` [PATCH] add sysfs misc device support [3/4] Greg KH
2003-12-23 0:28 ` [PATCH] add sysfs vc device support [4/4] Greg KH
2003-12-23 13:17 ` Christoph Hellwig
2003-12-23 0:29 ` [PATCH] add sysfs misc device support [3/4] Greg KH
2003-12-23 13:16 ` Christoph Hellwig
2003-12-23 13:15 ` [PATCH] add sysfs mem device support [2/4] Christoph Hellwig
2003-12-23 15:31 ` Rob Love
2003-12-23 16:07 ` Rob Love [this message]
2003-12-23 16:39 ` Christoph Hellwig
2003-12-23 17:56 ` Rob Love
2003-12-23 20:00 ` Stephan Maciej
2003-12-23 20:33 ` viro
2003-12-25 17:48 ` Andreas Jellinghaus
2003-12-25 18:45 ` Christoph Hellwig
2003-12-25 19:41 ` Martin Schlemmer
2003-12-25 20:57 ` Martin J. Bligh
2003-12-25 22:02 ` Martin Schlemmer
2003-12-26 16:19 ` Christoph Hellwig
2003-12-26 16:54 ` Tomasz Torcz
2003-12-26 20:18 ` Martin Schlemmer
2003-12-23 18:01 ` Greg KH
2003-12-23 19:16 ` Christoph Hellwig
2003-12-23 19:19 ` Rob Love
2003-12-23 19:22 ` Christoph Hellwig
2003-12-23 19:25 ` Rob Love
2003-12-23 19:42 ` Jeff Garzik
2003-12-23 19:45 ` Rob Love
2003-12-23 19:24 ` viro
2003-12-23 19:28 ` Rob Love
2003-12-23 11:07 ` [PATCH] some sysfs patches for 2.6.0 [0/4] Andreas Jellinghaus
2003-12-23 23:26 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 0:26 [PATCH] add sysfs mem device support [2/4] Greg KH
2003-12-23 13:15 ` Christoph Hellwig
2003-12-23 15:31 ` Rob Love
2003-12-23 16:07 ` Rob Love
2003-12-23 16:39 ` Christoph Hellwig
2003-12-23 17:56 ` Rob Love
2003-12-23 18:01 ` Greg KH
2003-12-23 19:16 ` Christoph Hellwig
2003-12-23 19:19 ` Rob Love
2003-12-23 19:22 ` Christoph Hellwig
2003-12-23 19:24 ` viro
2003-12-23 19:25 ` Rob Love
2003-12-23 19:28 ` Rob Love
2003-12-23 19:42 ` Jeff Garzik
2003-12-23 19:45 ` Rob Love
2003-12-23 20:00 ` Stephan Maciej
2003-12-23 20:33 ` viro
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=1072195665.3472.13.camel@fur \
--to=rml@ximian.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.