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: <1179073116.3723.45.camel@mulgrave.il.steeleye.com>
Date:	Sun, 13 May 2007 11:18:35 -0500
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	Dave Jones <davej@...hat.com>
Cc:	"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, 2007-05-13 at 11:10 -0500, James Bottomley wrote:
> > -	depends on SCSI
> > +	depends on SCSI_SCAN_ASYNC
> 
> No.  SCSI_SCAN_ASYNC is a bool ... if you depend on it, you'll force the
> wait scan to be built in, which isn't the idea at all.

Plus SCSI_SCAN_ASYNC only sets the *default* for async scanning.  You
can alter this at boot time, so you could need the wait scan module even
with it set to N.

James


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