From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM defconfig files
Date: Wed, 14 Jul 2010 15:20:46 +0200 [thread overview]
Message-ID: <20100714132046.GA18343@pengutronix.de> (raw)
In-Reply-To: <201007121634.04427.davidb@codeaurora.org>
On Mon, Jul 12, 2010 at 04:34:04PM -0700, David Brown wrote:
> On Monday 12 July 2010 16:18:01 Linus Torvalds wrote:
>
> > 2010/7/12 David Brown <davidb@codeaurora.org>:
> > >
> > > 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.
Note that no kernel is built at all, only the config is regenerated once
for each line.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-07-14 13:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100603074548.GA12104@flint.arm.linux.org.uk>
[not found] ` <alpine.LFD.2.00.1006030725420.8175@i5.linux-foundation.org>
[not found] ` <20100603181010.GA25779@flint.arm.linux.org.uk>
[not found] ` <1275589230.23384.19.camel@c-dwalke-linux.qualcomm.com>
[not found] ` <alpine.LFD.2.00.1006031119440.8175@i5.linux-foundation.org>
2010-06-14 8:32 ` ARM defconfig files Uwe Kleine-König
2010-06-30 10:40 ` Uwe Kleine-König
2010-07-12 15:55 ` Uwe Kleine-König
2010-07-12 16:51 ` Linus Torvalds
2010-07-12 17:32 ` Russell King - ARM Linux
2010-07-12 17:40 ` Linus Torvalds
2010-07-12 18:50 ` Uwe Kleine-König
2010-07-12 19:04 ` Linus Torvalds
2010-07-12 19:17 ` Nicolas Pitre
2010-07-12 19:34 ` Linus Torvalds
2010-07-12 19:50 ` Grant Likely
2010-07-13 7:07 ` Uwe Kleine-König
2010-07-13 8:07 ` optimized script [Was: ARM defconfig files] Uwe Kleine-König
2010-07-13 18:04 ` Olof Johansson
2010-07-13 23:39 ` Nicolas Pitre
2010-07-13 18:32 ` ARM defconfig files Grant Likely
2010-07-12 19:59 ` Uwe Kleine-König
2010-07-12 20:14 ` Nicolas Pitre
2010-07-12 19:09 ` Nicolas Pitre
2010-07-12 20:31 ` Arnd Bergmann
2010-07-12 20:50 ` Nicolas Pitre
2010-07-12 23:05 ` David Brown
2010-07-12 23:18 ` Linus Torvalds
2010-07-12 23:34 ` David Brown
2010-07-13 0:55 ` Nicolas Pitre
2010-07-14 9:13 ` Felipe Contreras
2010-07-14 13:20 ` Uwe Kleine-König [this message]
2010-07-14 17:37 ` Tony Luck
2010-07-13 18:32 ` Rob Landley
2010-07-12 20:06 ` Russell King - ARM Linux
2010-07-12 20:29 ` Nicolas Pitre
2010-07-12 21:54 ` Linus Torvalds
2010-07-14 9:21 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100714132046.GA18343@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).