From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wolverine01.qualcomm.com ([199.106.114.254]:40961 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755492Ab0FCTfp (ORCPT ); Thu, 3 Jun 2010 15:35:45 -0400 Subject: Re: ARM defconfig files From: Daniel Walker In-Reply-To: References: <20100603074548.GA12104@flint.arm.linux.org.uk> <20100603181010.GA25779@flint.arm.linux.org.uk> <20100603185333.GD25779@flint.arm.linux.org.uk> Content-Type: text/plain; charset="UTF-8" Date: Thu, 03 Jun 2010 12:35:42 -0700 Message-ID: <1275593742.23384.48.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: Linus Torvalds Cc: Russell King , Kevin Hilman , Linux Kernel Mailing List , linux-arm-msm@vger.kernel.org On Thu, 2010-06-03 at 11:56 -0700, Linus Torvalds wrote: > > On Thu, 3 Jun 2010, Russell King wrote: > > > > No amount of reorganising the Kconfig files into a heirarchial manner > > (which they already are) helps. Not one bit. Because they already are. > > That's not where the problem is. > > I don't think you read the whole thread. > > Earlier on, I explained exactly what I wanted: just add some "select" > statements to pickt he things you need per the particular target > configuration. You seem to have missed that part. > > In other words, you _can_ encode the information that is in the > xyz_defconfig files by doing it in Kconfig.xyz files instead. But you do > it in a human-readable manner. And the hierarchical thing is absolutely > required for that - otherwise you'd end up with just another form of the > current xyz_defconfig. > > See? > > In other words, you should be able to basically use "make allnoconfig" > together with a Kconfig.xyz file input to select _exactly_ the pieces you > need, and nothing else. If you did this for drivers, what about disabling a driver? If we used "select" wouldn't that force all the drivers on without allowing it to be unselected? Daniel