All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.5.26 hotplug failure
Date: Thu, 19 Sep 2002 16:06:44 -0700	[thread overview]
Message-ID: <20020919230643.GD18000@kroah.com> (raw)
In-Reply-To: <200209200656.23956.bhards@bigpond.net.au>

On Fri, Sep 20, 2002 at 06:56:23AM +1000, Brad Hards wrote:
> On Fri, 20 Sep 2002 02:49, Greg KH wrote:
> > The main reason is this information is no longer available to the USB
> > core.  It isn't keeping a list of registered drivers anymore, only the
> > driver core is.  So there's no way that usbfs can get to that
> > information.  As the info is available in driverfs, duplication of it in
> > usbfs would be bloat.
> This doesn't follow. driverfs != driver core, just as usbfs != USB core.

I agree.  But the info is now in the driver core, it's not present in
the USB core at all anymore.  So since drverfs exports what's in the
driver core, that info shows up there.  usbfs doesn't have access to
this info, so it can't display it.

> I wasn't joking about putting back the /proc/bus/usb/drivers file. This is 
> really going to hurt us in 2.6. 

Is this file _really_ used?  All it did was show the USB drivers
registered.  Even so, that same information is now present in driverfs,
I haven't taken away anything, just moved it.  Lots of things are
starting to move to driverfs, this isn't the first, and will not be the
last.

thanks,

greg k-h

  reply	other threads:[~2002-09-19 23:01 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 [this message]
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
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=20020919230643.GD18000@kroah.com \
    --to=greg@kroah.com \
    --cc=bhards@bigpond.net.au \
    --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 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.