James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> writes: >> When configuring MODULES with the kernel to be able to load external >> drivers coming as modules, but not using anything as module in the kernel >> itself, one would expect to end up in a module-free kernel. Currently, you >> don't if you use SCSI. You'll get one unnecessary module. > This isn't right because SCSI_SCAN_ASYNC only sets the *default* > behaviour of the kernel. Even if it's n the user can still boot up with > async scans by setting the kernel parameter. Ok, understood. But has it to be a module then? Why not giving the choice between building it directly into the kernel or as a module? > It also keeps coming up regularly: Well, then something doesn't seem to be ok, does it? ;-) Ingo Signed-off-by: Ingo Brueckl <ib@xxxxxxxxxxxxxxx> --- linux-2.6.28/drivers/scsi/Kconfig.orig 2008-12-25 00:26:37.000000000 +0100 +++ linux-2.6.28/drivers/scsi/Kconfig 2009-03-10 08:11:38.000000000 +0100 @@ -257,10 +257,14 @@ config SCSI_SCAN_ASYNC or async on the kernel's command line. config SCSI_WAIT_SCAN - tristate - default m + tristate "SCSI wait scanning" depends on SCSI depends on MODULES + help + If you are using a SCSI module and do asynchronous SCSI scanning + (either by having selected SCSI_SCAN_ASYNC or by specifying + "scsi_mod.scan=async" on the kernel's command line), you MUST say Y + here. menu "SCSI Transports" depends on SCSI -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
