From: Greg KH <greg@kroah.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Rob Landley <rob@landley.net>, Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org,
Michael-Luke Jones <mlj28@cam.ac.uk>,
Krzysztof Halasa <khc@pm.waw.pl>, Rod Whitby <rod@whitby.id.au>,
Russell King <rmk@arm.linux.org.uk>,
david@lang.hm
Subject: Re: Documentation for sysfs, hotplug, and firmware loading.
Date: Fri, 20 Jul 2007 01:09:36 -0700 [thread overview]
Message-ID: <20070720080936.GA22047@kroah.com> (raw)
In-Reply-To: <20070720095401.68e9ce03@gondolin.boeblingen.de.ibm.com>
On Fri, Jul 20, 2007 at 09:54:01AM +0200, Cornelia Huck wrote:
> On Fri, 20 Jul 2007 00:00:01 -0700,
> Greg KH <greg@kroah.com> wrote:
>
> > > I don't insist on it, mknod insists on it. You cannot mknod a dev node
> > > without specifying block or char.
> > >
> > > You're saying that sysfs should provide major and minor numbers without
> > > anywhere specifying "char" or "block", meaning the major and minor numbers
> > > cannot be _used_. I am insisting on getting the third piece of information
> > > without which "major" and "minor" are useless.
> > >
> > > I asked very specifically about this at OLS, several times. What you're
> > > telling me now seems to contradict what you told me then.
> >
> > Here's the rule:
> > If the SUBSYSTEM is "block", it's a block device. Otherwise
> > it's a char device.
>
> That's actually quite confusing to the casual reader, since:
>
> > But also realize that the majority of events you will get have nothing
> > to do with device nodes. I think you are forgetting this fact.
>
> So the rule should be:
> If the SUBSYSTEM is "block" (implying major/minor are provided),
> it's a block device.
> If the SUBSYSTEM is not "block", and major/minor are provided,
> it's a char device.
> If major/minor are not provided, the event/device is not
> relevant to device node creation.
Yes, that is much more descriptive, thanks.
greg k-h
next prev parent reply other threads:[~2007-07-20 8:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 21:03 Documentation for sysfs, hotplug, and firmware loading Rob Landley
2007-07-17 21:55 ` Randy Dunlap
2007-07-18 7:58 ` Cornelia Huck
2007-07-18 17:39 ` Rob Landley
2007-07-18 23:33 ` Kay Sievers
2007-07-20 5:14 ` Rob Landley
2007-07-20 7:00 ` Greg KH
2007-07-20 7:54 ` Cornelia Huck
2007-07-20 8:09 ` Greg KH [this message]
2007-07-21 3:48 ` Rob Landley
2007-07-21 6:23 ` Rob Landley
2007-07-18 23:40 ` Greg KH
2007-07-21 0:37 ` Rob Landley
2007-07-19 8:16 ` Cornelia Huck
2007-07-21 0:21 ` Rob Landley
2007-07-21 0:43 ` Greg KH
2007-07-23 23:26 ` Rob Landley
2007-07-24 7:38 ` Cornelia Huck
2007-07-21 0:49 ` Greg KH
2007-07-21 0:52 ` Greg KH
2007-07-21 6:32 ` Rob Landley
2007-07-18 10:33 ` Kay Sievers
[not found] <8I2t1-7jt-5@gated-at.bofh.it>
[not found] ` <8IlPa-3Gl-61@gated-at.bofh.it>
[not found] ` <8IzyM-86P-47@gated-at.bofh.it>
[not found] ` <8Jb1c-7vL-3@gated-at.bofh.it>
[not found] ` <8Jbuh-84N-3@gated-at.bofh.it>
2007-07-21 12:14 ` Bodo Eggert
2007-07-23 21:49 ` Rob Landley
2007-08-05 12:57 ` Bodo Eggert
2007-07-24 6:38 ` Greg KH
2007-07-25 19:28 ` Rob Landley
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=20070720080936.GA22047@kroah.com \
--to=greg@kroah.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@lang.hm \
--cc=kay.sievers@vrfy.org \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mlj28@cam.ac.uk \
--cc=rmk@arm.linux.org.uk \
--cc=rob@landley.net \
--cc=rod@whitby.id.au \
/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.