From: Sam Ravnborg <sam@ravnborg.org>
To: maximilian attems <maks@sternwelten.at>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Bastian Blank <waldi@debian.org>
Subject: Re: [patch] kbuild: add automatic updateconfig target
Date: Wed, 18 Jan 2006 21:42:34 +0100 [thread overview]
Message-ID: <20060118204234.GC14340@mars.ravnborg.org> (raw)
In-Reply-To: <20060118194056.GA26532@nancy>
On Wed, Jan 18, 2006 at 08:40:56PM +0100, maximilian attems wrote:
> From: Bastian Blank <waldi@debian.org>
>
> current hack for daily build linux-2.6-git is quite ugly:
> yes "n" | make oldconfig
>
> belows target helps to build git snapshots in a more automated way,
> setting the new options to their default.
Please always add Roman Zippel when dealing with kconfig changes.
We had a similar though more advanced proposal named miniconfig a month
or so ago but Roman had some grief with it so it was not applied.
I've let Roman decide on this one too.
Nitpicking below.
Sam
> +updateconfig: $(obj)/conf
> + $< -U arch/$(ARCH)/Kconfig
The other methods uses small letters so please change to '-u'
> - set_random
> + set_random,
> + update_default,
Keep same naming as the others. May I suggest set_default.
You did not introduce a specific update.config file like for the other
targets. Any reason for that?
Sam
next prev parent reply other threads:[~2006-01-18 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 19:40 [patch] kbuild: add automatic updateconfig target maximilian attems
2006-01-18 20:42 ` Sam Ravnborg [this message]
2006-01-18 20:47 ` Sam Ravnborg
2006-01-18 22:32 ` maximilian attems
2006-01-18 22:52 ` maximilian attems
2006-01-19 10:13 ` Bastian Blank
2006-01-19 11:50 ` Roman Zippel
2006-01-19 17:37 ` maximilian attems
2006-01-19 17:51 ` Roman Zippel
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=20060118204234.GC14340@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maks@sternwelten.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