From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] nanopi_m1{, _plus}_defconfig: U-Boot needs pylibfdt
Date: Fri, 11 Aug 2017 15:30:06 +0200 [thread overview]
Message-ID: <20170811153006.053e3329@windsurf> (raw)
In-Reply-To: <20170810215929.13430-1-arnout@mind.be>
Hello,
On Thu, 10 Aug 2017 23:59:29 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> nanopi_m1 and nanopi_m1_plus are sunxi boards that need pylibfdt in
> U-Boot.
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/27873655
> https://gitlab.com/buildroot.org/buildroot/-/jobs/27873656
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Chakra Divi <2chakrass@gmail.com>
> ---
> Apparently this was only tested on a host that had pylibfdt installed?
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:[~2017-08-11 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 21:59 [Buildroot] [PATCH] nanopi_m1{, _plus}_defconfig: U-Boot needs pylibfdt Arnout Vandecappelle
2017-08-11 13:30 ` 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=20170811153006.053e3329@windsurf \
--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