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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0705131757320.9570@yvahk01.tjqt.qr>
Date:	Sun, 13 May 2007 17:58:48 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: why does x86 "make defconfig" build a single, lonely module?


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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/