From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] boot/uboot: add support for the kconfig infrastructure
Date: Sun, 14 Jun 2015 15:18:05 +0200 [thread overview]
Message-ID: <1434287885.20201.3.camel@embedded.rocks> (raw)
In-Reply-To: <20150614144621.45e7c13b@free-electrons.com>
Dear Thomas Petazzoni,
On So, 2015-06-14 at 14:46 +0200, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Sun, 14 Jun 2015 14:05:57 +0200, J?rg Krause wrote:
> > With the patchset "kconfig: turnaround into single .config"
> > [http://lists.denx.de/pipermail/u-boot/2015-February/205490.html]
> > U-Boot switched to a single .config file for board configuration.
> > This allows
> > us to use the kconfig-package infrastructure.
> >
> > For providing backward compatibility with older U-Boot version a
> > user choice
> > between the new Kconfig and the legacy build system is introduced.
> > Kconfig
> > is chosen as default build system.
>
> This will break plenty of existing configuration that use older
> Buildroot versions. Since the legacy configure/build commands also
> work
> with newer U-Boot, I think we should rather have the legacy build
> logic
> used by default.
Sorry, I forgot to discard this sentence from the commit log. Indeed,
Kconfig is _not_ chosen as default.
> > This patch supersedes "boot/uboot: Add support for Kbuild & Kconfig
> > build
> > system" [http://patchwork.ozlabs.org/patch/436498/]
>
> Please mark your patches as Superseded yourself in patchwork :-)
Done :-)
> No need to indicate that in the commit log.
Okay.
Best regards
J?rg Krause
prev parent reply other threads:[~2015-06-14 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 12:05 [Buildroot] [PATCH v3 1/2] boot/uboot: add support for the kconfig infrastructure Jörg Krause
2015-06-14 12:05 ` [Buildroot] [PATCH v3 2/2] docs/manual: add U-Boot configuration Jörg Krause
2015-06-14 12:46 ` [Buildroot] [PATCH v3 1/2] boot/uboot: add support for the kconfig infrastructure Thomas Petazzoni
2015-06-14 13:18 ` Jörg Krause [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=1434287885.20201.3.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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