From mboxrd@z Thu Jan 1 00:00:00 1970 From: nico@fluxnic.net (Nicolas Pitre) Date: Mon, 12 Jul 2010 20:55:26 -0400 (EDT) Subject: ARM defconfig files In-Reply-To: <201007121634.04427.davidb@codeaurora.org> References: <201007121605.32462.davidb@codeaurora.org> <201007121634.04427.davidb@codeaurora.org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, 12 Jul 2010, David Brown wrote: > On Monday 12 July 2010 16:18:01 Linus Torvalds wrote: > > > 2010/7/12 David Brown : > > > > > > Do you have scripts or tools that you did this with, or is a manual > > > process. We're about to add several new (ARM) targets, and it'd be > > > nice to be able to make small defconfigs for those targets as well. > > > > Uwe posted it earlier in this thread as an attachement, and I put the > > python script into the merge commit message too. And we should > > probably put it somewhere in scripts too, and/or make a 'make' target > > to create the small config files. > > > > I pushed it all out, and tagged it as -rc5. > > Got it, thanks. I just pulled a bit soon. > > It seems a bit brute force, probably not something I can make part of > our regular build process, but I can definitely run it before sending > patches out. > > I wonder if there's a more efficient way of doing it that doesn't > involve invoking make for each line of the file. It at least > shouldn't be necessary to actually build the kernel each time. I'm sure that some clever people will come up with a better script eventually. Maybe this could even be generated by scripts/kconfig/conf directly. Nicolas