From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-scsi@vger.kernel.org
Cc: Simon Arlott <simon@fire.lp0.eu>,
James Bottomley <james.bottomley@steeleye.com>,
Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel-packagers@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: [PATCH] SCSI: Let users disable SCSI_WAIT_SCAN to be built
Date: Tue, 15 May 2007 23:56:32 +0200 (CEST) [thread overview]
Message-ID: <tkrat.99c0f1a1898aa67f@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070515172905.GJ10562@parisc-linux.org>
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
drivers/scsi/Kconfig | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
Index: linux-2.6.22-rc1/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.22-rc1.orig/drivers/scsi/Kconfig
+++ linux-2.6.22-rc1/drivers/scsi/Kconfig
@@ -241,11 +241,19 @@ config SCSI_SCAN_ASYNC
You can override this choice by specifying "scsi_mod.scan=sync"
or async on the kernel's command line.
-config SCSI_WAIT_SCAN
+config SCSI_WAIT_SCAN_NO_Y
tristate
default m
- depends on SCSI
- depends on MODULES
+
+config SCSI_WAIT_SCAN
+ tristate "Pseudo driver which waits for SCSI scanning to finish"
+ depends on MODULES && SCSI && SCSI_WAIT_SCAN_NO_Y
+ help
+ When loaded, this module will do nothing else than wait for
+ SCSI low-level drivers to finish asynchronous scanning.
+ The module will be called scsi_wait_scan.
+
+ Most people can say n here.
menu "SCSI Transports"
depends on SCSI
Is there a better way to restrict SCSI_WAIT_SCAN to m and n?
--
Stefan Richter
-=====-=-=== -=-= -====
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-05-15 21:57 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 15:22 why does x86 "make defconfig" build a single, lonely module? Robert P. J. Day
2007-05-13 15:58 ` Jan Engelhardt
2007-05-13 16:06 ` Dave Jones
2007-05-13 16:10 ` James Bottomley
2007-05-13 16:18 ` James Bottomley
2007-05-13 16:30 ` Dave Jones
2007-05-14 9:35 ` Satyam Sharma
2007-05-14 9:45 ` Satyam Sharma
2007-05-14 12:00 ` Satyam Sharma
2007-05-14 12:23 ` Satyam Sharma
2007-05-14 14:31 ` James Bottomley
2007-05-15 0:41 ` Satyam Sharma
2007-05-15 11:26 ` Simon Arlott
2007-05-15 12:02 ` Asynchronous scsi scanning Matthew Wilcox
2007-05-15 16:30 ` Simon Arlott
2007-05-15 17:29 ` Matthew Wilcox
2007-05-15 21:56 ` Stefan Richter [this message]
2007-05-16 14:43 ` [PATCH] SCSI: Let users disable SCSI_WAIT_SCAN to be built Stefan Richter
2007-05-17 14:00 ` James Bottomley
2007-05-17 17:02 ` Satyam Sharma
2007-05-15 23:27 ` Asynchronous scsi scanning Satyam Sharma
2007-05-15 23:28 ` Arjan van de Ven
2007-05-15 23:49 ` Satyam Sharma
2007-05-16 2:51 ` Matthew Wilcox
2007-05-16 2:59 ` Roland Dreier
2007-05-17 17:13 ` Satyam Sharma
2007-05-17 17:20 ` Matthew Wilcox
2007-05-17 17:41 ` Satyam Sharma
2007-05-17 18:24 ` Christoph Hellwig
2007-05-17 18:47 ` Satyam Sharma
2007-05-17 18:51 ` Christoph Hellwig
2007-05-17 19:04 ` Satyam Sharma
2007-05-17 19:39 ` Matthew Wilcox
2007-05-17 19:43 ` Benjamin LaHaise
2007-05-17 21:30 ` Matthew Wilcox
2007-05-17 21:42 ` Dave Jones
2007-05-17 22:00 ` Peter Jones
2007-05-18 14:00 ` Stefan Richter
2007-05-18 5:28 ` Satyam Sharma
2007-05-18 11:24 ` Matthew Wilcox
2007-05-18 13:14 ` Satyam Sharma
2007-05-18 3:41 ` Satyam Sharma
2007-05-18 11:19 ` Matthew Wilcox
2007-05-18 13:06 ` Satyam Sharma
2007-05-17 17:32 ` sysfs makes scaling suck " Benjamin LaHaise
2007-05-17 17:45 ` James Bottomley
2007-05-17 17:49 ` Benjamin LaHaise
2007-05-19 16:30 ` Greg KH
2007-05-17 22:24 ` Peter Jones
2007-05-13 16:20 ` why does x86 "make defconfig" build a single, lonely module? Robert P. J. Day
2007-05-13 16:27 ` James Bottomley
2007-05-13 16:37 ` Robert P. J. Day
2007-05-13 17:42 ` Simon Arlott
2007-05-13 17:48 ` James Bottomley
2007-05-13 18:26 ` Simon Arlott
2007-05-13 18:45 ` Dave Jones
2007-05-13 18:45 ` James Bottomley
2007-05-14 17:29 ` Jan Engelhardt
2007-05-14 18:46 ` Alan Cox
2007-05-14 20:06 ` Jan Engelhardt
2007-05-13 16:28 ` Dave Jones
2007-05-13 20:38 ` Simon Arlott
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=tkrat.99c0f1a1898aa67f@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=davej@redhat.com \
--cc=james.bottomley@steeleye.com \
--cc=kernel-packagers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=simon@fire.lp0.eu \
/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®