From: Greg KH <greg@kroah.com>
To: Paul Zimmerman <Paul_Zimmerman@inSilicon.com>
Cc: "'linux-usb-devel@lists.sourceforge.net'"
<linux-usb-devel@lists.sourceforge.net>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] USB device support for 2.5.8
Date: Wed, 17 Apr 2002 14:15:59 -0700 [thread overview]
Message-ID: <20020417211559.GB2365@kroah.com> (raw)
In-Reply-To: <7FD8B823E5024E44B027221DEB34C087536510@scl-exch.phoenix.com>
On Wed, Apr 17, 2002 at 02:09:32PM -0700, Paul Zimmerman wrote:
> We already have drivers/usb/hcd for "host controller drivers", how about
> drivers/usb/dcd for "device controller drivers"?
No, the drivers/usb/hcd directory has been moved to drivers/usb/host,
and a few more files were added to it. Take a look at the drivers/usb/
restructure in 2.5.8.
thanks,
greg k-h
next prev parent reply other threads:[~2002-04-17 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 21:09 [linux-usb-devel] Re: [BK PATCH] USB device support for 2.5.8 Paul Zimmerman
2002-04-17 21:15 ` Greg KH [this message]
[not found] <1018997778.2989@whiskey.enposte.net>
2002-04-17 4:10 ` Stuart Lynne
-- strict thread matches above, loose matches on Subject: below --
2002-04-16 22:54 Greg KH
2002-04-16 22:58 ` Greg KH
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=20020417211559.GB2365@kroah.com \
--to=greg@kroah.com \
--cc=Paul_Zimmerman@inSilicon.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