From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:59955 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750970Ab0FCVRh (ORCPT ); Thu, 3 Jun 2010 17:17:37 -0400 Date: Fri, 4 Jun 2010 00:17:09 +0300 From: Tony Lindgren Subject: Re: ARM defconfig files Message-ID: <20100603211707.GA6499@atomide.com> References: <20100603074548.GA12104@flint.arm.linux.org.uk> <20100603181010.GA25779@flint.arm.linux.org.uk> <20100603185333.GD25779@flint.arm.linux.org.uk> <1275593742.23384.48.camel@c-dwalke-linux.qualcomm.com> <20100603194559.GF25779@flint.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: Linus Torvalds Cc: Russell King , Daniel Walker , Kevin Hilman , Linux Kernel Mailing List , linux-arm-msm@vger.kernel.org * Linus Torvalds [100603 23:30]: > > and now you'd be able to basically generate a OMAP3EVM .config file by > just running "allnoconfig" on that Kconfig.omap3_evm file. But it would > only have to select the parts that are specific for the EVM platform, > because the generic OMAP3 support would be picked by the Kconfig.omap3 > file, which in turn would not have to worry about the generic ARM parts > etc. > > See? Sounds like a good improvment to me. Tony