From: Michal Marek <mmarek@suse.cz>
To: maximilian attems <max@stro.at>
Cc: linux-kbuild@vger.kernel.org, Bastian Blank <waldi@debian.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Kconfig add reportoldconfig and updateoldconfig targets
Date: Mon, 13 Sep 2010 16:54:13 +0200 [thread overview]
Message-ID: <4C8E3B15.2040807@suse.cz> (raw)
In-Reply-To: <20100913143830.GK2919@stro.at>
On 13.9.2010 16:38, maximilian attems wrote:
> From: Bastian Blank <waldi@debian.org>
>
> This patch has been around for a looong time in Debian kernels
> and might be useful for others. The reportoldconfig target
> is used for the official linux-2.6 image builds. It outputs
> to the build log the changed configs and sets any unset to
> it's default.
2.6.26-rc1 has listnewconfig and oldnoconfig, which do more or less the
same. And I think we have enough *config targets already, so unless
there is a problem that is hard to solve with the current kconfig plus
some scripting (*), I'd vote for not adding further special-purpose
*config targets.
(*) Such as the defconfig cleanup that took hours with a brute-force
python script, but was easily achieved by a patch that added the
savedefconfig target.
Michal
next prev parent reply other threads:[~2010-09-13 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 14:38 Kconfig add reportoldconfig and updateoldconfig targets maximilian attems
2010-09-13 14:54 ` Michal Marek [this message]
2010-09-14 3:50 ` [PATCH 1/2] Kbuild: Treat KBUILD_DEFCONFIG=old as request to use .config as the base Ben Hutchings
2010-10-01 14:05 ` Michal Marek
2010-10-01 22:47 ` Ben Hutchings
2010-10-02 12:14 ` Sam Ravnborg
2010-09-14 3:52 ` [PATCH 2/2] Kbuild: kconfig: Verbose version of --listnewconfig and --defconfig Ben Hutchings
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=4C8E3B15.2040807@suse.cz \
--to=mmarek@suse.cz \
--cc=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
--cc=waldi@debian.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