Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: kory.maincent@bootlin.com
Cc: thomas.petazzoni@bootlin.com,
	Sergey Matyukevich <geomatsi@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/4] boot/arm-trusted-firmware: update condition for custom tarball management
Date: Sat, 23 Jul 2022 22:12:35 +0200	[thread overview]
Message-ID: <20220723201235.GL2641@scaer> (raw)
In-Reply-To: <20220623140028.1315712-1-kory.maincent@bootlin.com>

Köry, All,

On 2022-06-23 16:00 +0200, Kory Maincent via buildroot spake thusly:
> From: Kory Maincent <kory.maincent@bootlin.com>
> 
> This patch updates the condition to handle custom tarballs as specified by
> the configuration. This change is made to have cleaner condition and for
> consistency.
> 
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>

Series of 4 patches applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
> 
> Notes:
>     This patch is based on this other one:
>     https://lists.buildroot.org/pipermail/buildroot/2022-June/645216.html
> 
>  boot/arm-trusted-firmware/arm-trusted-firmware.mk | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
> index 965b1a2eb5..421d8c770d 100644
> --- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk
> +++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
> @@ -6,7 +6,7 @@
>  
>  ARM_TRUSTED_FIRMWARE_VERSION = $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_VERSION))
>  
> -ifeq ($(ARM_TRUSTED_FIRMWARE_VERSION),custom)
> +ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL),y)
>  # Handle custom ATF tarballs as specified by the configuration
>  ARM_TRUSTED_FIRMWARE_TARBALL = $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL_LOCATION))
>  ARM_TRUSTED_FIRMWARE_SITE = $(patsubst %/,%,$(dir $(ARM_TRUSTED_FIRMWARE_TARBALL)))
> @@ -190,7 +190,7 @@ endef
>  # Configuration check
>  ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE)$(BR_BUILDING),yy)
>  
> -ifeq ($(ARM_TRUSTED_FIRMWARE_VERSION),custom)
> +ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL),y)
>  ifeq ($(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL_LOCATION)),)
>  $(error No tarball location specified. Please check BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL_LOCATION)
>  endif
> -- 
> 2.25.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-07-23 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 14:00 [Buildroot] [PATCH 1/4] boot/arm-trusted-firmware: update condition for custom tarball management Kory Maincent via buildroot
2022-06-23 14:00 ` [Buildroot] [PATCH 2/4] boot/u-boot: " Kory Maincent via buildroot
2022-06-23 14:00 ` [Buildroot] [PATCH 3/4] boot/barebox: " Kory Maincent via buildroot
2022-06-23 14:00 ` [Buildroot] [PATCH 4/4] boot/opensbi: " Kory Maincent via buildroot
2022-07-23 20:12 ` Yann E. MORIN [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=20220723201235.GL2641@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=geomatsi@gmail.com \
    --cc=kory.maincent@bootlin.com \
    --cc=thomas.petazzoni@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