Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757760AbXEMRnL (ORCPT ); Sun, 13 May 2007 13:43:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753995AbXEMRm5 (ORCPT ); Sun, 13 May 2007 13:42:57 -0400 Received: from proxima.lp0.eu ([85.158.45.36]:34476 "EHLO proxima.lp0.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006AbXEMRm4 (ORCPT ); Sun, 13 May 2007 13:42:56 -0400 Message-ID: <46474E1A.6080904@simon.arlott.org.uk> Date: Sun, 13 May 2007 18:42:50 +0100 From: Simon Arlott User-Agent: Thunderbird 1.5.0.5 (X11/20060819) MIME-Version: 1.0 To: James Bottomley CC: "Robert P. J. Day" , Dave Jones , Linux Kernel Mailing List , linux-scsi@vger.kernel.org Subject: Re: why does x86 "make defconfig" build a single, lonely module? References: <20070513160608.GA29024@redhat.com> <1179072655.3723.42.camel@mulgrave.il.steeleye.com> <1179073670.3723.48.camel@mulgrave.il.steeleye.com> In-Reply-To: <1179073670.3723.48.camel@mulgrave.il.steeleye.com> X-Enigmail-Version: 0.94.1.2 OpenPGP: id=89C93563 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1435 Lines: 34 On 13/05/07 17:27, James Bottomley wrote: > On Sun, 2007-05-13 at 12:20 -0400, Robert P. J. Day wrote: >> since this thread looks like it's going to get away from me in a >> hurry :-), my only point in asking was to point out that that lone >> module was the only thing preventing the build from being module-free. >> >> i'm not saying that that's *necessarily* a good thing, but it just >> strikes me as odd that, out of all of the possible modules that might >> be selected in a default config for x86, this was the *only* one that >> was picked. >> >> i just think it's a bit weird, that's all. > > It's designed on the predicate that people who want to be module free > will actually set CONFIG_MODULE=n. > > If you set CONFIG_MODULE=y and build SCSI we assume you could have a > SCSI driver module at some point, which would necessitate the wait scan > module. This should be implemented like "Library routines" and only added if such a SCSI driver module is actually selected. Why can't it at least be a visible option in the menu? (Although even then it looks like it's impossible to disable). Why does ATA select SCSI anyway? Surely PATA doesn't require it? -- Simon Arlott - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/