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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20070513184504.GH27604@redhat.com>
Date:	Sun, 13 May 2007 14:45:04 -0400
From:	Dave Jones <davej@...hat.com>
To:	Simon Arlott <simon@...e.lp0.eu>
Cc:	James Bottomley <James.Bottomley@...elEye.com>,
	"Robert P. J. Day" <rpjday@...dspring.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org
Subject: Re: why does x86 "make defconfig" build a single, lonely module?

On Sun, May 13, 2007 at 07:26:31PM +0100, Simon Arlott wrote:

 > It looks like SCSI_WAIT_SCAN is pointless unless SCSI_SCAN_ASYNC 
 > is selected - so it should depend on it:
 > 
 > ---
 > diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
 > index e62d23f..0f6c370 100644
 > --- a/drivers/scsi/Kconfig
 > +++ b/drivers/scsi/Kconfig
 > @@ -244,7 +244,7 @@ config SCSI_SCAN_ASYNC
 >  config SCSI_WAIT_SCAN
 >  	tristate
 >  	default m
 > -	depends on SCSI
 > +	depends on SCSI_SCAN_ASYNC
 >  	depends on MODULES
 >  
 >  menu "SCSI Transports"

This is the same broken patch that I posted earlier in this thread.
See James' follow-ups to my mail.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/