linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aleksey Gorelov" <Aleksey_Gorelov@Phoenix.com>
To: <stern@rowland.harvard.edu>, <mdharm-usb@one-eyed-alien.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: 
Date: Wed, 2 Feb 2005 16:17:13 -0800	[thread overview]
Message-ID: <5F106036E3D97448B673ED7AA8B2B6B301B3CD73@scl-exch2k.phoenix.com> (raw)

Hi Matt, Alan, 

  Could you please tell me (link would do) why it makes default
delay_use=5 
really necessary (from the patch below)?
https://lists.one-eyed-alien.net/pipermail/usb-storage/2004-August/00074
7.html

It makes USB boot really painfull and slow :(

  I understand there should be a good reason for it. I've tried to find
an answer in 
archives, without much success though.

Thanks,
Aleks.

             reply	other threads:[~2005-02-03  0:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  0:17 Aleksey Gorelov [this message]
2005-02-03  1:12 ` your mail Matthew Dharm
2005-02-03 16:03 ` Alan Stern

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=5F106036E3D97448B673ED7AA8B2B6B301B3CD73@scl-exch2k.phoenix.com \
    --to=aleksey_gorelov@phoenix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --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).