All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Add out-of-source U-Boot device tree support
Date: Wed, 5 Apr 2017 22:30:24 +0200	[thread overview]
Message-ID: <20170405223024.1d43de2b@free-electrons.com> (raw)
In-Reply-To: <1491363951-3971-1-git-send-email-james@balean.com.au>

Hello,

On Tue,  4 Apr 2017 22:45:51 -0500, James Balean wrote:
> Similaly to Linux, this patch adds the ability to copy in and build
> out-of-source device tree sources during a U-Boot build.
> 
> Signed-off-by: James Balean <james@balean.com.au>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Changes for v2:
>   - Added dependency on U-Boot Kconfig build system.
>   - Code style cleanup

Applied to master after slightly tweaking the help text and dropping a
needlessly added newline at the end of Config.in.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2017-04-05 20:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  6:12 [Buildroot] [PATCH] Add out-of-source U-Boot device tree support James Balean
2017-03-27 12:12 ` Arnout Vandecappelle
2017-03-28  1:19   ` James Balean
2017-03-28  6:14   ` James Balean
2017-03-28  9:01     ` Arnout Vandecappelle
2017-03-28 19:53       ` Thomas Petazzoni
2017-03-28 20:19         ` Arnout Vandecappelle
2017-03-28 20:29           ` Thomas Petazzoni
2017-03-28 22:17             ` Arnout Vandecappelle
2017-03-29  7:09               ` Thomas Petazzoni
2017-04-05  3:29                 ` James Balean
2017-04-05  3:45                   ` [Buildroot] [PATCH v2] " James Balean
2017-04-05 20: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=20170405223024.1d43de2b@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 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.