From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] olimex_a20_olinuxino_lime2_defconfig: correct u-boot configuration
Date: Fri, 23 Dec 2016 00:06:48 +0100 [thread overview]
Message-ID: <20161223000648.3d5a9eb5@free-electrons.com> (raw)
In-Reply-To: <20161221211621.8851-1-peter@korsgaard.com>
Hello,
On Wed, 21 Dec 2016 22:16:21 +0100, Peter Korsgaard wrote:
> This defconfig currently doesn't build:
> https://travis-ci.org/buildroot/buildroot-defconfig-testing/jobs/185616951
>
> As u-boot needs dtc, so add that and change to kconfig mode like on our
> other allwinner defconfigs as that is in fact what is used.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> configs/olimex_a20_olinuxino_lime2_defconfig | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-12-22 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 21:16 [Buildroot] [PATCH] olimex_a20_olinuxino_lime2_defconfig: correct u-boot configuration Peter Korsgaard
2016-12-22 23:06 ` 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=20161223000648.3d5a9eb5@free-electrons.com \
--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