public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig bug
Date: Sat, 27 Oct 2007 13:26:50 +0100	[thread overview]
Message-ID: <200710271326.51136.nick@ukfsn.org> (raw)
In-Reply-To: <200710201257.55616.nick@ukfsn.org>

[-- Attachment #1: Type: text/plain, Size: 551 bytes --]

Am I the only one seeing this issue?

On Saturday 20 October 2007 12:57:55 Nick Warne wrote:
> Hi all,
>
> I noticed I had a module option being built that wasn't in menuconfig.
>
> It is missing description.  I also added a brief help message.
>
> Signed off by:  Nick Warne <nick@ukfsn.org>


Not using this patch, using menuconfig the scsi_wait option doesn't appear 
anywhere for me to be able to it turn off - yet grep'ing .config will always 
show this option as being built as a module.

Nick
-- 
Free Software Foundation Associate Member 5508

[-- Attachment #2: scsi_wait.patch --]
[-- Type: text/x-diff, Size: 682 bytes --]

--- linux-current/drivers/scsi/Kconfig_old	2007-10-20 12:44:50.000000000 +0100
+++ linux-current/drivers/scsi/Kconfig	2007-10-20 12:57:13.000000000 +0100
@@ -248,10 +248,17 @@
 	  or async on the kernel's command line.
 
 config SCSI_WAIT_SCAN
-	tristate
+	tristate "Wait for SCSI scan completion"
 	default m
 	depends on SCSI
 	depends on MODULES
+	help
+	  The SCSI subsystem can probe for devices while the rest of the
+	  system continues booting, and even probe devices on different
+	  busses in parallel, leading to a significant speed-up.
+
+	  You can load the scsi_wait_scan module to ensure that all scans
+	  have completed.
 
 menu "SCSI Transports"
 	depends on SCSI

      parent reply	other threads:[~2007-10-27 12:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 11:57 [PATCH] Kconfig bug Nick Warne
2007-10-20 12:42 ` tristate and bool not enogh for Kconfig anymore Henrik Carlqvist
2007-10-20 19:17   ` Sam Ravnborg
2007-10-20 21:56     ` Randy Dunlap
2007-10-21  4:47     ` Valdis.Kletnieks
2007-10-21 10:24       ` Henrik Carlqvist
2007-10-21 16:45         ` Randy Dunlap
2007-10-21 20:42           ` Henrik Carlqvist
2007-10-21 21:03           ` Sam Ravnborg
2007-10-22  0:47             ` Randy Dunlap
2007-10-22  3:14               ` Randy Dunlap
2007-10-22  4:42                 ` Randy Dunlap
2007-10-27 23:37                 ` Roman Zippel
2007-10-22 10:11   ` Christoph Hellwig
2007-10-22 10:32     ` Alexander E. Patrakov
2007-10-22 10:57       ` Christoph Hellwig
2007-10-22 11:27         ` Alexander E. Patrakov
2007-10-22 12:53           ` Christoph Hellwig
2007-10-22 13:18             ` Alexander E. Patrakov
2007-10-22 11:46   ` Helge Hafting
2007-10-22 21:50     ` Henrik Carlqvist
2007-10-27 12:26 ` Nick Warne [this message]

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=200710271326.51136.nick@ukfsn.org \
    --to=nick@ukfsn.org \
    --cc=linux-kernel@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