From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Roman Zippel <zippel@linux-m68k.org>,
Michal Marek <mmarek@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] kconfig: introduce alldefconfig + savedefconfig
Date: Wed, 28 Jul 2010 08:47:23 +0200 [thread overview]
Message-ID: <20100728064723.GA14914@pengutronix.de> (raw)
In-Reply-To: <20100725213808.GA5814@merkur.ravnborg.org>
Hi Sam,
On Sun, Jul 25, 2010 at 11:38:08PM +0200, Sam Ravnborg wrote:
> After reading some of the mails about the
> defconfig files I decided to take a look at kconfig.
>
> We already decided to go for a solution where the defconfig
> files contains only the minimal configuration.
> Uwe developed a script to assist but having native support
> in kconfig is preferable.
>
> This patch set introduce "alldefconfig".
> alldefconfig create a configuration with all values set
> to default values.
> This can be usefull when we check if we do have a sane
> set of default values. Rhe config can be inspected
> using menuconfig.
>
> The patches also introduce "savedefconfig" which
> reads the current configuration and save it
> as a minimal configuration.
>
> In my testing I benchmarked it with one
> of the arm defconfings and the final result is
> the same (symbols appear in different order).
I would prefer to have them in the same order. I havn't checked the
details, but I really like getting support for minimal defconfigs done
in kconfig directly.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2010-07-28 6:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 21:38 [RFC] kconfig: introduce alldefconfig + savedefconfig Sam Ravnborg
2010-07-25 21:38 ` [PATCH 1/4] kconfig: save location of config symbols Sam Ravnborg
2010-07-25 21:39 ` [PATCH 2/4] kconfig: print more info when we see a recursive dependency Sam Ravnborg
2010-07-25 21:39 ` [PATCH 3/4] kconfig: add alldefconfig Sam Ravnborg
2010-07-25 21:40 ` [PATCH 4/4] kconfig: add savedefconfig Sam Ravnborg
2010-07-27 15:42 ` Michal Marek
2010-07-27 16:50 ` Sam Ravnborg
2010-07-28 20:36 ` [RFC PATCH] kconfig: use long options in conf Sam Ravnborg
2010-07-29 8:13 ` Sam Ravnborg
2010-07-29 8:15 ` [PATCH 1/2] kconfig: rename loose_nonint_oldconfig => oldnoconfig Sam Ravnborg
2010-07-29 8:16 ` [PATCH 2/2] kconfig: change nonint_oldconfig to listnewconfig Sam Ravnborg
2010-07-29 9:23 ` [RFC PATCH] kconfig: use long options in conf Michal Marek
2010-07-29 14:47 ` Aristeu Rozanski
2010-07-29 15:04 ` Michal Marek
2010-07-29 15:16 ` Aristeu Rozanski
2010-07-29 19:34 ` Sam Ravnborg
2010-07-29 19:50 ` Aristeu Rozanski
2010-07-29 23:04 ` Sam Ravnborg
2010-07-30 14:53 ` Aristeu Rozanski
2010-07-29 9:17 ` Michal Marek
2010-07-29 9:39 ` Sam Ravnborg
2010-07-29 10:08 ` Michal Marek
2010-07-29 14:30 ` Randy Dunlap
2010-07-29 19:29 ` Sam Ravnborg
2010-07-25 22:20 ` [RFC] kconfig: introduce alldefconfig + savedefconfig Sam Ravnborg
2010-07-28 6:47 ` Uwe Kleine-König [this message]
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=20100728064723.GA14914@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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