From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot/uboot: default to kconfig buildsystem for latest version
Date: Wed, 25 Apr 2018 21:35:50 +0200 [thread overview]
Message-ID: <20180425213550.361af846@windsurf> (raw)
In-Reply-To: <20180424163410.16587-1-yann.morin.1998@free.fr>
Hello,
On Tue, 24 Apr 2018 18:34:10 +0200, Yann E. MORIN wrote:
> By default, the builsystem for uboot defaults to 'legacy', while the
> default version is very well capable of using the 'kconfig' buildsystem
> instead.
>
> Having the 'legacy' buildsystem be the default in that case makes it
> quite inconvenient for users: they would expect to be able to use e.g.
> uboot-menuconfig et al. with the default uboot version.
>
> Switch to using 'kconfig' when we use the latest version. Keep the
> 'legacy' as default for everything else.
>
> Also, invert the 'legacy' and 'kconfig' entries in the choice: it is
> nicer to have the recent and future-proodf entry first.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> boot/uboot/Config.in | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-25 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 16:34 [Buildroot] [PATCH] boot/uboot: default to kconfig buildsystem for latest version Yann E. MORIN
2018-04-25 6:39 ` Petr Vorel
2018-04-25 6:43 ` Yegor Yefremov
2018-04-25 19:35 ` Thomas Petazzoni [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=20180425213550.361af846@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.