All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Patrick Mochel <mochel@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: 2.5.26 hotplug failure
Date: Tue, 24 Sep 2002 12:29:56 -0700	[thread overview]
Message-ID: <20020924192956.GA25963@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0209241146520.7652-100000@penguin.transmeta.com>

On Tue, Sep 24, 2002 at 11:55:00AM -0700, Linus Torvalds wrote:
> 
> So I'd suggest you just export a text-file that describes the thing. 
> Something like
> 
>  - legacy name (the kernel knows about these anyway, see /proc/mounts and 
>    friends)

I would like to see all of the /proc/mounts and friends info that
"knows" about the legacy name, to disappear if possible.  Yes, I know
the root filesystem logic will have to stay, but I don't want to see
this be used like the devfs name is used throughout the kernel.  That
info should not be in the kernel, it's up to the user what to name their
"USB mouse, connected to the EHCI host controller's 3 hub port".

>  - major number, minor number) and char vs block

Yes, this info is needed, and if presented in a file, that would be
fine.  It was just that the device node was a nice compact version of
this :)
But I can see how the device node would be abused, and it's fine with me
if it isn't present in driverfs.

thanks,

greg k-h

  reply	other threads:[~2002-09-24 19:25 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
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 [this message]
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=20020924192956.GA25963@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=torvalds@transmeta.com \
    /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.