From: Alan Jenkins <sourcejedi.lkml@googlemail.com>
To: David VomLehn <dvomlehn@cisco.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
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, 07 Aug 2009 21:09:40 +0100 [thread overview]
Message-ID: <4A7C8A04.3060005@googlemail.com> (raw)
In-Reply-To: <20090807174209.GB30450@cuplxvomd02.corp.sa.net>
David VomLehn wrote:
> On Fri, Aug 07, 2009 at 06:17:51PM +0100, Alan Jenkins wrote:
>
>> On 8/7/09, Alan Stern <stern@rowland.harvard.edu> wrote:
>>
>>> On Fri, 7 Aug 2009, Alan Jenkins wrote:
>>>
>>>
>>>>> +/* 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.
> I remember thinking about this and seem to recall that Alan Stern and I
> tossed this idea around, but didn't act on it. Such a thing holds potential
> for avoiding an unnecessary delay during boot. Whether it actually makes
> things faster in a given configuration will depend on that configuration's
> critical path, but I would welcome such a patch on the basis that it's
> unlikely to hurt and could improve boot times in some circumstances.
>
Bother, I see why this doesn't work now. There are all the USB
*wireless* network drivers outside the menu.
Thanks anyway
Alan
prev parent reply other threads:[~2009-08-07 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 22:15 [PATCH 2/7 v3] initdev:kernel:USB init device discovery notification David VomLehn
2009-08-07 15:32 ` Alan Jenkins
2009-08-07 15:44 ` Alan Stern
2009-08-07 17:17 ` Alan Jenkins
[not found] ` <9b2b86520908071017h606e595fr4488d6ff61cb337c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-07 17:42 ` David VomLehn
2009-08-07 20:09 ` Alan Jenkins [this message]
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=4A7C8A04.3060005@googlemail.com \
--to=sourcejedi.lkml@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=alan-jenkins@tuffmail.co.uk \
--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 \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).