Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757944AbYAFOKq (ORCPT ); Sun, 6 Jan 2008 09:10:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753925AbYAFOKi (ORCPT ); Sun, 6 Jan 2008 09:10:38 -0500 Received: from einhorn.in-berlin.de ([192.109.42.8]:49928 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752945AbYAFOKh (ORCPT ); Sun, 6 Jan 2008 09:10:37 -0500 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <4780E0F7.100@s5r6.in-berlin.de> Date: Sun, 06 Jan 2008 15:08:55 +0100 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071216 SeaMonkey/1.1.7 MIME-Version: 1.0 To: david@lang.hm CC: Adrian Bunk , Randy Dunlap , Sam Ravnborg , Al Boldi , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, David Brownell , Greg KH , Andrew Morton Subject: Re: [PATCH 2/5] USB Kconfig: Select SCSI for USB Mass Storage support References: <200801051546.SAA08947@raad.intranet> <20080105113024.209485f5.randy.dunlap@oracle.com> <20080105210330.GC22232@does.not.exist> <20080105210940.GA10302@uranus.ravnborg.org> <47801126.7020807@oracle.com> <20080105234540.GG22232@does.not.exist> <47802249.9010107@s5r6.in-berlin.de> <20080106005807.GH22232@does.not.exist> <4780C728.1030806@s5r6.in-berlin.de> <20080106123728.GD2082@does.not.exist> <4780D3E5.20908@s5r6.in-berlin.de> <4780DA92.6050403@s5r6.in-berlin.de> In-Reply-To: X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1034 Lines: 27 david@lang.hm wrote: > On Sun, 6 Jan 2008, Stefan Richter wrote: >> build-time configuration has to deal with different, more >> complex questions than run-time configuration. ... > what config options must be selected by the user at build time? (i.e. no > sane default can possibly be deduced from the hardware) > > there are a lot of options that, if selected, will affect the final > result significantly. but I can't think of any that can't have a > reasonable default. ... I agree that sets of defaults, e.g. based on usage profiles, help a lot. Alas the 'select' keyword enforces one particular profile. (And it is currently broken and generally dangerous and inefficient for dependencies deeper than one level.) -- Stefan Richter -=====-==--- ---= --==- http://arcgraph.de/sr/ -- 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/