Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] boot/arm-trusted-firmware: Add out-of-source ATF device tree support
Date: Thu, 19 Aug 2021 23:27:46 +0200	[thread overview]
Message-ID: <20210819232746.5995c5e9@windsurf> (raw)
In-Reply-To: <20210709094925.1605675-2-kory.maincent@bootlin.com>

On Fri,  9 Jul 2021 11:49:25 +0200
Kory Maincent <kory.maincent@bootlin.com> wrote:

> Similarly to Uboot, this patch adds the ability to copy in and build
> out-of-source device tree sources during an ATF build.
> 
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
>  boot/arm-trusted-firmware/Config.in               | 9 +++++++++
>  boot/arm-trusted-firmware/arm-trusted-firmware.mk | 5 +++++
>  2 files changed, 14 insertions(+)

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-08-19 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09  9:49 [Buildroot] [PATCH 1/2] boot/arm-trusted-firmware: Update FIP image generation with BL33_CFG option Kory Maincent
2021-07-09  9:49 ` [Buildroot] [PATCH 2/2] boot/arm-trusted-firmware: Add out-of-source ATF device tree support Kory Maincent
2021-08-19 21:27   ` Thomas Petazzoni [this message]
2021-08-17  9:13 ` [Buildroot] [PATCH 1/2] boot/arm-trusted-firmware: Update FIP image generation with BL33_CFG option Köry Maincent
2021-08-19 21:26 ` Thomas Petazzoni
2021-08-31  8:51   ` Köry Maincent

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=20210819232746.5995c5e9@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=kory.maincent@bootlin.com \
    /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