From mboxrd@z Thu Jan 1 00:00:00 1970 From: dwalker@codeaurora.org (Daniel Walker) Date: Tue, 08 Jun 2010 16:26:58 -0700 Subject: Heads up: Linus plans to kill ARM defconfigs In-Reply-To: <4C0ED074.7050700@bluewatersys.com> References: <4C083BCF.2060500@bluewatersys.com> <201006040310.15019.marek.vasut@gmail.com> <4C0853E1.1080005@bluewatersys.com> <20100604061034.GI6499@atomide.com> <20100608115832.GB25370@n2100.arm.linux.org.uk> <4C0E3CAF.4050409@weinigel.se> <20100608131007.GE25370@n2100.arm.linux.org.uk> <4C0EAD3B.8010404@bluewatersys.com> <4C0ED074.7050700@bluewatersys.com> Message-ID: <1276039618.14529.30.camel@c-dwalke-linux.qualcomm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, 2010-06-09 at 11:21 +1200, Ryan Mallon wrote: > Nicolas Pitre wrote: > > On Wed, 9 Jun 2010, Ryan Mallon wrote: > > > >> Striping the spitz defconfig back for example: > >> > >> ryan at okiwi:configs$ wc -l spitz_defconfig > >> 1820 spitz_defconfig > >> > >> ryan at okiwi:configs$ grep -v "is not set" spitz_defconfig | grep -v > >> "^#" | wc -l > >> 641 > >> > >> So removing all the comments and non-set options makes the defconfig > >> about 1/3 the size. If the defconfigs were generated by hand, or a > >> proper set of tools, then they could be much less verbose and diffs for > >> things like adding or removing a single config option would actually be > >> readable. > >> > >> If we want to have individual board configurations in the kernel, then > >> the information has to live somewhere. Whether it is defconfig, KConfig, > >> Documentation, whatever, the information will still take up a similar > >> amount of space, and the process of moving the information will generate > >> a load of diffstat noise. > > > > Did you see the SheevaPlug example I posted earlier? It contains only > > 10 lines of added information. Certainly not similar amount of space to > > the existing defconfig files. > > > > Yes. I thought the problem was that Kconfig doesn't work correctly for > this though. Does having 'select MTD_PARTITIONS' automatically cause > CONFIG_MTD to be set? If not, then you basically need to have the full > config option list, which is basically what defconfig is. Yeah, you need all the dependencies .. At least in my testing you do, since select doesn't auto-select dependencies .. It's still smaller than the normal defconfig tho. Daniel