From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: [PATCH 0/7] driver core: export MAJOR/MINOR to the hotplug env
Date: Sun, 23 Jan 2005 05:19:11 +0100 [thread overview]
Message-ID: <20050123041911.GA9209@vrfy.org> (raw)
This patch sequence moves the creation of the sysfs "dev" file of the class
devices into the driver core. The struct class_device contains a dev_t
value now. If set, the driver core will create the "dev" file containing
the major/minor numbers automatically.
The MAJOR/MINOR values are also exported to the hotplug environment. This
makes it easy for userspace, especially udev to know if it should wait for
a "dev" file to create a device node or if it can just ignore the event.
We currently carry a compiled in blacklist around for that reason.
It would also be possible to run some "tiny udev" while sysfs is not
available - just by reading the hotplug call or the netlink-uevent.
Thanks,
Kay
next reply other threads:[~2005-01-23 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 4:19 Kay Sievers [this message]
2005-02-01 22:56 ` [PATCH 0/7] driver core: export MAJOR/MINOR to the hotplug env Greg KH
2005-02-02 0:48 ` Kay Sievers
2005-02-05 6:16 ` Greg KH
2005-02-05 21:49 ` Kay Sievers
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=20050123041911.GA9209@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.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 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.