From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 3] linux: add linux-update-config and linux-update-defconfig targets
Date: Tue, 27 Sep 2011 22:46:03 +0200 [thread overview]
Message-ID: <20110927224603.02a7e0b1@skate> (raw)
In-Reply-To: <81756817dc47990f5c42.1317151269@localhost6.localdomain6>
Le Tue, 27 Sep 2011 21:21:09 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> In analogy to build targets uclibc-update and busybox-update, add
> extra targets to copy the current configuration to the custom
> configuration file set in buildroot. These targets facilitate the
> work of developers adding support for a specific board.
>
> linux-update-config copies .config directly.
> linux-update-defconfig first creates a defconfig and copies that.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
As further improvements, I am wondering :
* Whether linux-update-*config should display a warning/error when
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE is not used, instead of being
silent.
* Whether this configuration update shouldn't be done automatically
when one does "make linux-menuconfig" or "make linux-xconfig".
People have often found strange to loose their configuration changes
in Linux/Busybox/uClibc when they do a make clean.
But regardless of this discussion, I think your patch should be merged
as is.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-27 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 19:21 [Buildroot] [PATCH 0 of 3] Add/rename *-update-config targets Thomas De Schampheleire
2011-09-27 19:21 ` [Buildroot] [PATCH 1 of 3] linux: add linux-update-config and linux-update-defconfig targets Thomas De Schampheleire
2011-09-27 20:46 ` Thomas Petazzoni [this message]
2011-09-28 6:08 ` Thomas De Schampheleire
2011-09-30 19:56 ` Thomas Petazzoni
2011-09-30 20:02 ` Thomas De Schampheleire
2011-09-27 19:21 ` [Buildroot] [PATCH 2 of 3] busybox: rename busybox-update to busybox-update-config Thomas De Schampheleire
2011-09-27 20:46 ` Thomas Petazzoni
2011-09-27 19:21 ` [Buildroot] [PATCH 3 of 3] uclibc: rename uclibc-update to uclibc-update-config Thomas De Schampheleire
2011-09-27 20:46 ` Thomas Petazzoni
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=20110927224603.02a7e0b1@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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