From: Christoph Hellwig <hch@infradead.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] add sysfs misc device support [3/4]
Date: Tue, 23 Dec 2003 13:16:58 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107218549017430@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107213951618305@msgid-missing>
On Mon, Dec 22, 2003 at 04:28:00PM -0800, Greg KH wrote:
> This adds /sys/class/mem which enables all misc char devices to show up
> properly in udev.
>
> Note, the misc_init() call has been moved to a subsys_initcall as it
> seems there are a lot of platform specific misc devices that are calling
> misc_register before misc_init() is called.
>
> Has been posted to lkml a few times in the past and tested by a wide
> range of people.
So how are misc devices a device class now? This is just a random coolection
of drivers that traditionally didn't have their own major. Killing misc
devices sounds like abetter plan than codifying this in sysfs..
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2003-12-23 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:28 [PATCH] add sysfs misc device support [3/4] Greg KH
2003-12-23 0:29 ` Greg KH
2003-12-23 13:16 ` Christoph Hellwig [this message]
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=marc-linux-hotplug-107218549017430@msgid-missing \
--to=hch@infradead.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).