From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: Brad Hards <bhards@bigpond.net.au>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: 2.5.26 hotplug failure
Date: Fri, 20 Sep 2002 20:58:09 -0700 [thread overview]
Message-ID: <3D8BEE51.1020304@pacbell.net> (raw)
In-Reply-To: 20020921033137.GA26017@kroah.com
Greg KH wrote:
> On Fri, Sep 20, 2002 at 07:55:22PM -0700, David Brownell wrote:
>
>>How about a facility to create the character (or block?) special file
>>node right there in the driverfs directory? Optional of course.
>
>
> No, Linus has stated that this is not ok to do. See the lkml archives
> for the whole discussion about this.
I suspected that'd be the case. Some pointer into the archives
would be good, though I'd suspect the basic summary is that it'd
be too much like devfs that way. Did the same statement apply to
adding some file that wasn't a device special file? That kind
of solution moves in the "no majors/minors" direction, which I
thought was the general goal. Leaves a naming policy debate,
but one that ought to be more managable (say, with devlabel).
Though I guess my original reaction still stands then: I don't
much want to care about major/minor numbers, so why not just leave
them out in favor of whatever better solution is the goal? Save
everyone the intermediate steps!
- Dave
next prev parent reply other threads:[~2002-09-21 3:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 7:50 2.5.26 hotplug failure Duncan Sands
2002-07-18 18:36 ` Greg KH
2002-07-18 19:07 ` Duncan Sands
2002-09-15 21:53 ` Duncan Sands
2002-09-18 6:52 ` Greg KH
2002-09-18 7:15 ` [linux-usb-devel] " Brad Hards
2002-09-18 16:55 ` Greg KH
2002-09-19 7:37 ` Daniel Phillips
2002-09-19 7:45 ` Daniel Phillips
2002-09-19 7:48 ` Greg KH
2002-09-19 7:55 ` Daniel Phillips
2002-09-19 16:49 ` Greg KH
2002-09-19 20:56 ` Brad Hards
2002-09-19 23:06 ` Greg KH
2002-09-20 20:42 ` [linux-usb-devel] " David Brownell
2002-09-20 23:11 ` Greg KH
2002-09-21 2:55 ` David Brownell
2002-09-21 3:31 ` Greg KH
2002-09-21 3:58 ` David Brownell [this message]
2002-09-21 5:48 ` Greg KH
2002-09-22 1:21 ` Linus Torvalds
2002-09-24 18:26 ` Patrick Mochel
2002-09-24 18:55 ` Linus Torvalds
2002-09-24 19:29 ` Greg KH
2002-09-24 22:37 ` Patrick Mochel
2002-09-20 23:22 ` Brad Hards
2002-09-20 23:36 ` Johannes Erdfelt
2002-09-21 0:11 ` Randy.Dunlap
2002-09-21 0:25 ` Brad Hards
2002-09-21 2:36 ` David Brownell
2002-09-20 23:46 ` Patrick Mochel
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=3D8BEE51.1020304@pacbell.net \
--to=david-b@pacbell.net \
--cc=bhards@bigpond.net.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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).