On Tue, 2009-03-10 at 08:00 +0100, Ingo Brueckl wrote: > 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? If you read through the threads, that question is answered. > > It also keeps coming up regularly: > > Well, then something doesn't seem to be ok, does it? ;-) James -- 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
