From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@suse.de>,
mochel@osdl.org, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driverfs support for USB - take 2
Date: Tue, 29 Jan 2002 17:09:22 -0800 [thread overview]
Message-ID: <20020130010921.GB22131@kroah.com> (raw)
In-Reply-To: <20020130002418.GB21784@kroah.com> <20020130020312.C16379@suse.de>
In-Reply-To: <20020130020312.C16379@suse.de>
On Wed, Jan 30, 2002 at 02:03:12AM +0100, Dave Jones wrote:
>
> > Yes, I need to have better names for the devices than just "usb_bus",
> > any suggestions? These devices nodes are really the USB root hubs in
> > the USB controller, so they could just have the USB number as the name
> > like the other USB devices (001), but that's pretty boring :)
>
> "usb_root0" .. "usb_rootN" ?
Hm, that's a good idea, it would match the usbfs bus numbers which
should keep people happy.
> btw, a script to marry the busid's from driverfs to lspci/lsusb
> output may be useful in the future especially if combined somehow
> with tree(1). Could be very handy when it gets time to debug
> those "My system won't suspend to disk" "What does /driver look like?"
> situations.
Ah, a lsdrivers program is needed! :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-01-30 1:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 0:24 Greg KH
2002-01-30 1:03 ` Dave Jones
2002-01-30 1:09 ` Greg KH [this message]
2002-01-30 1:19 ` Patrick Mochel
2002-01-30 2:15 ` [linux-usb-devel] " David Brownell
2002-01-30 4:09 ` Greg KH
2002-01-30 20:07 ` [linux-usb-devel] " David Brownell
2002-02-02 0:18 ` Greg KH
2002-02-02 19:13 ` David Brownell
2002-02-05 6:49 ` Greg KH
2002-01-30 1:49 ` [linux-usb-devel] " Stephen J. Gowdy
2002-01-30 4:10 ` Greg KH
2002-01-30 18:26 ` Patrick Mochel
2002-01-30 20:24 ` [linux-usb-devel] " David Brownell
2002-02-02 0:23 ` Greg KH
2002-02-02 19:27 ` David Brownell
2002-01-31 12:49 ` Pavel Machek
2002-02-01 9:27 ` Horst von Brand
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=20020130010921.GB22131@kroah.com \
--to=greg@kroah.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mochel@osdl.org \
/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®