public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] driver core: export MAJOR/MINOR to the hotplug env
Date: Tue, 1 Feb 2005 14:56:25 -0800	[thread overview]
Message-ID: <20050201225625.GA14962@kroah.com> (raw)
In-Reply-To: <20050123041911.GA9209@vrfy.org>

On Sun, Jan 23, 2005 at 05:19:11AM +0100, Kay Sievers wrote:
> 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.

This is great, thanks for doing this.  I've applied all of these patches
to my trees, and they'll show up in the next -mm release.

Hm, that class_simple interface is looking like the way we should move
toward, as it's "simple" to use, instead of the more complex class code.
I'll have to look at migrating more code to use it over time, or move
that interface back into the class code itself...

thanks,

greg k-h

  reply	other threads:[~2005-02-01 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23  4:19 [PATCH 0/7] driver core: export MAJOR/MINOR to the hotplug env Kay Sievers
2005-02-01 22:56 ` Greg KH [this message]
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=20050201225625.GA14962@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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