Messages in this thread | | | Date | Mon, 14 May 2007 15:15:04 +0530 | From | "Satyam Sharma" <> | Subject | Re: why does x86 "make defconfig" build a single, lonely module? |
| |
On 5/14/07, Satyam Sharma <satyam.sharma@gmail.com> wrote: > [...] > config SCSI_WAIT_SCAN > tristate > - default m > - depends on SCSI > - depends on MODULES > + default m if SCSI=m > + default n
Note that this also means SCSI_WAIT_SCAN=n (will not get compiled and built even as a module) if SCSI=y. But this is perfectly fine, because I see:
#ifndef MODULE late_initcall(scsi_complete_async_scans); #endif
in drivers/scsi/scsi_scan.c anyway, so the async scans will be waited upon and get complete even when SCSI=y and scsi_scan_type=async, i.e. you don't really need the scsi_wait_scan module in that case anyway.
Satyam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |