From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gw0-f46.google.com ([74.125.83.46]:42477 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752119Ab0GLTvI convert rfc822-to-8bit (ORCPT ); Mon, 12 Jul 2010 15:51:08 -0400 MIME-Version: 1.0 In-Reply-To: References: <20100603181010.GA25779@flint.arm.linux.org.uk> <1275589230.23384.19.camel@c-dwalke-linux.qualcomm.com> <20100614083214.GA2104@pengutronix.de> <20100630104043.GG11746@pengutronix.de> <20100712155518.GA24144@pengutronix.de> <20100712173228.GC9897@n2100.arm.linux.org.uk> <20100712185029.GB14425@pengutronix.de> From: Grant Likely Date: Mon, 12 Jul 2010 13:50:47 -0600 Message-ID: Subject: Re: ARM defconfig files Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: Linus Torvalds Cc: Nicolas Pitre , Daniel Walker , Russell King - ARM Linux , Kevin Hilman , linux-arm-msm@vger.kernel.org, Linux Kernel Mailing List , linux-omap@vger.kernel.org, =?ISO-8859-1?Q?Uwe_Kleine=2DK=F6nig?= , Eric Miao , linux-arm-kernel@lists.infradead.org On Mon, Jul 12, 2010 at 1:34 PM, Linus Torvalds wrote: > On Mon, Jul 12, 2010 at 12:17 PM, Nicolas Pitre wrote: >> I think Uwe could provide his script and add it to the kernel tree. >> Then all architectures could benefit from it.  Having the defconfig >> files contain only those options which are different from the defaults >> is certainly more readable, even on x86. > > Quite possible. But maintainers would need to be on the lookout of > people actually using the script, and refusing to apply patches that > re-introduce the whole big thing. I can (partially) speak for powerpc. If ARM uses this approach, then I think we can do the same. After the defconfigs are trimmed, I certainly won't pick up any more full defconfigs. Of course, I'm also operating under the assumption that this is a temporary measure until one of the better solutions is implemented. I do suspect that the trimmed defconfigs will tend to be unstable and will still require manual maintenance. I think the Kconfig fragments approach is the most promising if the dependencies issue can be solved. g.