From: Matthew Wilcox <matthew@wil.cx>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Fabio Comolli <fabio.comolli@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sam@ravnborg.org, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Possible bug in SCSI Kconfig
Date: Thu, 23 Oct 2008 11:39:18 -0600 [thread overview]
Message-ID: <20081023173917.GP26094@parisc-linux.org> (raw)
In-Reply-To: <4900B4B9.4050103@s5r6.in-berlin.de>
On Thu, Oct 23, 2008 at 07:30:33PM +0200, Stefan Richter wrote:
> - scsi_wait_scan is a special method to wait for devices during boot
> which only works with some hardware types. More general methods are
> available and have been in use far longer than scsi_wait_scan
> exists. Nobody fundamentally needs scsi_wait_scan, it is only a
> convenient tool for some users who choose to use it.
> Special features are traditionally per default off in Kconfig and
> are supposed to be actively enabled.
What 'general methods' would those be?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-10-23 17:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 16:29 Possible bug in SCSI Kconfig Fabio Comolli
2008-10-22 18:35 ` Stefan Richter
2008-10-22 19:29 ` Fabio Comolli
2008-10-22 19:05 ` James Bottomley
2008-10-22 19:25 ` Fabio Comolli
2008-10-22 19:26 ` Matthew Wilcox
2008-10-22 19:31 ` Fabio Comolli
2008-10-22 19:34 ` Matthew Wilcox
2008-10-22 19:45 ` Fabio Comolli
2008-10-22 19:44 ` James Bottomley
2008-10-22 19:48 ` Fabio Comolli
2008-10-23 17:30 ` Stefan Richter
2008-10-23 17:39 ` Matthew Wilcox [this message]
2008-10-23 18:59 ` Stefan Richter
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=20081023173917.GP26094@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.