mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: James.Bottomley@SteelEye.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bernhard Walle <bwalle@suse.de>
Subject: [PATCH] Allow SCSI_WAIT_SCAN to be deselected
Date: Thu, 13 Nov 2008 15:11:12 +0100	[thread overview]
Message-ID: <1226585472-12559-1-git-send-email-bwalle@suse.de> (raw)

This patch adds a proper help for SCSI_WAIT_SCAN and allows the module to be
deselected. I see no reason to force it being build. It also makes it
impossible to compile-in the module.


Signed-off-by: Bernhard Walle <bwalle@suse.de>
---
 drivers/scsi/Kconfig |   11 ++++++++---
 1 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index 403ecad..42b8355 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -257,10 +257,15 @@ config SCSI_SCAN_ASYNC
 	  or async on the kernel's command line.
 
 config SCSI_WAIT_SCAN
-	tristate
+	tristate "Module to wait until all the async scans are complete"
 	default m
-	depends on SCSI
-	depends on MODULES
+	depends on SCSI && m
+    help
+      This is a simple module to 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
-- 
1.6.0.2


             reply	other threads:[~2008-11-13 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 14:11 Bernhard Walle [this message]
2008-11-13 14:18 ` Fabio Comolli
2008-11-13 14:22   ` Dmitri Vorobiev
2008-11-14 12:23     ` Simon Arlott
2008-11-14 12:32       ` Dmitri Vorobiev

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=1226585472-12559-1-git-send-email-bwalle@suse.de \
    --to=bwalle@suse.de \
    --cc=James.Bottomley@SteelEye.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 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®