From: Johannes Erdfelt <johannes@erdfelt.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
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 19:36:42 -0400 [thread overview]
Message-ID: <20020920193642.I1627@sventech.com> (raw)
In-Reply-To: <200209210922.41887.bhards@bigpond.net.au>; from bhards@bigpond.net.au on Sat, Sep 21, 2002 at 09:22:41AM +1000
On Sat, Sep 21, 2002, Brad Hards <bhards@bigpond.net.au> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, 21 Sep 2002 06:42, David Brownell wrote:
> > >>I wasn't joking about putting back the /proc/bus/usb/drivers file. This
> > >> is really going to hurt us in 2.6.
> >
> > Considering that the main use of that file that I know about was
> > implicit (usbfs is available if its files are present, another
> > assumption broken in 2.5), I'm not sure I feel any pain... :-)
>
> OK. Everytime someone goes "I've got usbfs loaded, and here is
> /proc/bus/usb/devices, but can't send you /proc/bus/usb/drivers", I'll assume
> that you two will answer the question.
>
> Helping people is hard. Please don't make it harder. :-(
Personally, I've never used /proc/bus/usb/drivers. I've always just
looked at lsmod.
Why should this be any different?
JE
next prev parent reply other threads:[~2002-09-20 23:31 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
2002-09-24 22:37 ` Patrick Mochel
2002-09-20 23:22 ` Brad Hards
2002-09-20 23:36 ` Johannes Erdfelt [this message]
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=20020920193642.I1627@sventech.com \
--to=johannes@erdfelt.com \
--cc=bhards@bigpond.net.au \
--cc=david-b@pacbell.net \
--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 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.