From: Brad Hards <bhards@bigpond.net.au>
To: Greg KH <greg@kroah.com>, Duncan Sands <duncan.sands@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: 2.5.26 hotplug failure
Date: Wed, 18 Sep 2002 17:15:50 +1000 [thread overview]
Message-ID: <200209181715.51314.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020918065225.GB6840@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 18 Sep 2002 16:52, Greg KH wrote:
> On Sun, Sep 15, 2002 at 11:53:41PM +0200, Duncan Sands wrote:
> > A simple fix is to change the test to [ $COUNT -lt 2 ];
>
> Good catch, yes the drivers file disappeared, and until now, almost no
> one noticed it :)
I assume that /proc/bus/usb/drivers went to driverfs. Everyone likes the new
guy :)
I'd like the file back. We have a lot of debugging advice that asks people to
send that particular file to us, and it is very useful. Even if you update
the few places that you can find, then you will still have a lot of confusion
(well, if you have 2.4, then send this, and if you have 2.6, send this, and
if that doesn't exist, and you're on 2.4, mount this filesystem, else mount
this filesystem). Ugly, and increases the support workload.
A symlink will do, assuming both filesystems are mounted. If we only have
usbfs, I still want the data.
Please fix this before 2.6.
Brad
- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9iCgnW6pHgIdAuOMRAgRcAJ9+i0ksw2S4qS8wvA+SD5prjA4IEwCcCulE
APZsrWY1WlNoY42cG8pXUTI=
=GNYM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-18 7:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 7:50 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 ` Brad Hards [this message]
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
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=200209181715.51314.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=duncan.sands@wanadoo.fr \
--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
all inboxes | Powered by JetHome®