From: Alan Jenkins <sourcejedi.lkml@googlemail.com>
To: David VomLehn <dvomlehn@cisco.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-usb@vger.kernel.org, greg@kroah.com,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
arjan@infradead.org
Subject: Re: [PATCH 2/7 v3] initdev:kernel:USB init device discovery notification
Date: Fri, 7 Aug 2009 16:32:52 +0100 [thread overview]
Message-ID: <9b2b86520908070832p2d1658b0t8b1d89d1a034bb9a@mail.gmail.com> (raw)
In-Reply-To: <20090804221506.GA9256@cuplxvomd02.corp.sa.net>
On 8/4/09, David VomLehn <dvomlehn@cisco.com> wrote:
> From: Alan Stern <stern@rowland.harvard.edu>
>
> Use init device discovery infrastructure to provide notification of
> availability of USB devices.
>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: David VomLehn <dvomlehn@cisco.com>
> ---
> drivers/usb/core/hub.c | 26 ++++++++++++++++++++++++++
> 1 files changed, 26 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index be86ae3..08baee0 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -37,6 +37,20 @@
> #endif
> #endif
>
> +/* The mask of possible USB boot devices depends on what drivers and
> + * options have been configured into the kernel. There are too many
> + * USB network config options to list here, so just assume it is always
> + * possible to have a USB network device.
> + */
That could be fixed though. Make the "USB Network Adaptors" menu into
an option. Then you just have e.g. "CONFIG_NETDEV_USB", plus the two
class devices outside the menu (CONFIG_USB_ACM and CONFIG_USB_WDM).
Alan
next prev parent reply other threads:[~2009-08-07 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 22:15 David VomLehn
2009-08-07 15:32 ` Alan Jenkins [this message]
2009-08-07 15:44 ` Alan Stern
2009-08-07 17:17 ` Alan Jenkins
2009-08-07 17:42 ` David VomLehn
2009-08-07 20:09 ` Alan Jenkins
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=9b2b86520908070832p2d1658b0t8b1d89d1a034bb9a@mail.gmail.com \
--to=sourcejedi.lkml@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dvomlehn@cisco.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.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®