From: Changli Gao <xiaosuo@gmail.com>
To: James.Bottomley@HansenPartnership.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, xiaosuo <xiaosuo@gmail.com>
Subject: [PATCH] scsi_wait_scan: no option appears when configuring for scsi_wait_scan.
Date: Wed, 17 Jun 2009 10:07:32 +0800 [thread overview]
Message-ID: <4A384FE4.9090703@gmail.com> (raw)
FIXBUG: missing comment after tristate leads to no option for
scsci_wait_scan when configuring.
When build kernel, this module is always built if I choose SCSI, and I
can't find any option in the configuration menu, so I can't disable it
or build it into kernel statically. After diving into the kernel source
code, I found no comment after keyword tristate, then I added the
comment and help.
Signed-off-by: Changli Gao <xiaosuo@gmail.com <mailto:xiaosuo@gmail.com>>
----
Kconfig | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
--- drivers/scsi/Kconfig.orig 2009-06-17 09:52:46.000000000 +0800
+++ drivers/scsi/Kconfig 2009-06-17 09:55:57.000000000 +0800
@@ -259,10 +259,15 @@
or async on the kernel's command line.
config SCSI_WAIT_SCAN
- tristate
+ tristate "Wait until all the async scans are complete"
default m
depends on SCSI
depends on MODULES
+ help
+ Wait until all the async scans are complete. The idea is to use it in
+ initrd/initramfs scripts. You modprobe it after all the modprobes of
+ the root SCSI drivers and it will wait until they have all finished
+ scanning their busses before allowing the boot to proceed
menu "SCSI Transports"
depends on SCSI
next reply other threads:[~2009-06-17 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 2:07 Changli Gao [this message]
2009-06-17 2:12 ` [PATCH] scsi_wait_scan: no option appears when configuring for scsi_wait_scan Matthew Wilcox
2009-06-17 10:07 ` [PATCH] SCSI: explain the hidden scsi_wait_scan Kconfig variable Stefan Richter
2009-06-17 10:28 ` Stefan Richter
2009-06-18 0:57 ` Changli Gao
2009-06-18 15:21 ` James Bottomley
2009-06-18 16:59 ` Sam Ravnborg
2009-06-18 19:03 ` [PATCH update 1] " Stefan Richter
2009-06-18 19:03 ` [PATCH update 2] " Stefan Richter
2009-06-22 8:57 ` Alan Cox
2009-06-22 11:02 ` Matthew Wilcox
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=4A384FE4.9090703@gmail.com \
--to=xiaosuo@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.