Re: why does x86 "make defconfig" build a single, lonely module?

[Jan Engelhardt <jengelh@linux01.gwdg.de>]

On May 13 2007 11:22, Robert P. J. Day wrote:
>
>  not a big deal, but is there a reason that a "make defconfig" on my
>x86 system ends up selecting and building a single module?
>
>  Building modules, stage 2.
>  MODPOST 1 modules
>  CC      drivers/scsi/scsi_wait_scan.mod.o
>  LD [M]  drivers/scsi/scsi_wait_scan.ko
>
>is there something special about that module?  just curious.

$ make defconfig;
$ grep =m .config;
CONFIG_SCSI_WAIT_SCAN=m
$ grep -A2 SCSI_WAIT_SCAN drivers/scsi/Kconfig;
config SCSI_WAIT_SCAN
        tristate
        default m
$ grep SCSI_WAIT_SCAN arch/i386/Kconfig || echo "no result";
no result



	Jan
-- 
-
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/