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  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]
Date:	Sun, 13 May 2007 17:58:48 +0200 (MEST)
From:	Jan Engelhardt <>
To:	"Robert P. J. Day" <>
cc:	Linux Kernel Mailing List <>
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;
$ grep -A2 SCSI_WAIT_SCAN drivers/scsi/Kconfig;
        default m
$ grep SCSI_WAIT_SCAN arch/i386/Kconfig || echo "no result";
no result

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists