mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: James <bjlockie@lockie.ca>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: no modules :-)
Date: Sat, 25 Sep 2010 19:39:14 -0700	[thread overview]
Message-ID: <20100925193914.f3c919d1.rdunlap@xenotime.net> (raw)
In-Reply-To: <4C9D845A.4060105@lockie.ca>

On Sat, 25 Sep 2010 01:10:50 -0400 James wrote:

>  I don't like modules. :-)
> 
> What is pulling this in:
> 
> CONFIG_SCSI_WAIT_SCAN=m
> 
> I edited .config but make must have turned it back on.
> --

If you have SCSI enabled and MODULES enabled, this kconfig symbol will be
enabled (=m) automatically.  From drivers/scsi/Kconfig (with # comments):


config SCSI_WAIT_SCAN
	tristate  # No prompt here, this is an invisible symbol.
	default m
	depends on SCSI
	depends on MODULES
# scsi_wait_scan is a loadable module which waits 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 buses before allowing the boot to
# proceed.  (This method is not applicable if targets boot independently in
# parallel with the initiator, or with transports with non-deterministic target
# discovery schemes, or if a transport driver does not support scsi_wait_scan.)
#
# This symbol is not exposed as a prompt because little is to be gained by
# disabling it, whereas people who accidentally switch it off may wonder why
# their mkinitrd gets into trouble.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-26  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  5:10 James
2010-09-26  2:39 ` Randy Dunlap [this message]
2010-09-26 13:08 ` Sitsofe Wheeler
2010-09-26 10:55 Martin Rogge

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=20100925193914.f3c919d1.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=bjlockie@lockie.ca \
    --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

all inboxes | Powered by JetHome®