From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Simon Arlott" Subject: Re: why does x86 "make defconfig" build a single, lonely module? Date: Tue, 15 May 2007 12:26:29 +0100 Message-ID: <17841.simon.1179228389@5ec7c279.invalid> References: <20070513160608.GA29024@redhat.com> <1179072655.3723.42.camel@mulgrave.il.steeleye.com> <1179073116.3723.45.camel@mulgrave.il.steeleye.com> <1179153096.3703.23.camel@mulgrave.il.steeleye.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from proxima.lp0.eu ([85.158.45.36]:44257 "EHLO proxima.lp0.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755936AbXEOL0g (ORCPT ); Tue, 15 May 2007 07:26:36 -0400 In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Satyam Sharma Cc: James Bottomley , Dave Jones , "Robert P. J. Day" , Linux Kernel Mailing List , linux-scsi@vger.kernel.org On Tue, May 15, 2007 01:41, Satyam Sharma wrote: > On 5/14/07, James Bottomley wrote: >> On Mon, 2007-05-14 at 17:53 +0530, Satyam Sharma wrote: >> > > I guess this is probably the behaviour that James wanted originally? >> >> No ... you're still not reading the explanation in the thread: >> >> The wait scan module is designed to wait for scans of driver modules. >> Whether SCSI=y or m has no effect on this ... you can still have modular >> drivers with built in SCSI. > > Ah, I see why we _want_ this built as a _module_ only, and don't even > want to expose the Kconfig option to the user, lest he screw himself later. > But dangling "default m"'s or "default y"'s not exposed to the user do > stand out discomfortingly in Kconfigs, wish there was a better way to > handle this. I've already suggested a sysfs attribute - or something equivalent - would be much better. It's just one function that a user might want to run multiple times (e.g. after adding scsi devices?) - why should loading a module be used for this? -- Simon Arlott