Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bryan Brattlof via buildroot <buildroot@buildroot.org>
Cc: "Vincent Stehlé" <vincent.stehle@arm.com>,
	"Marleen Vos" <marleen.vos@mind.be>, "Bryan Brattlof" <bb@ti.com>,
	"Sergey Matyukevich" <geomatsi@gmail.com>,
	"Xuanhao Shi" <X15000177@gmail.com>,
	"Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
	"Ariel D'Alessandro" <ariel@vanguardiasur.com.ar>,
	"Romain Naour" <romain.naour@gmail.com>,
	"Michael Trimarchi" <michael@amarulasolutions.com>,
	"Anand Gadiyar" <gadiyar@ti.com>
Subject: Re: [Buildroot] [PATCH v2 1/4] boot/arm-trusted-firmware: move to official source for tf-a
Date: Thu, 8 Aug 2024 00:12:30 +0200	[thread overview]
Message-ID: <20240808001230.39ca2187@windsurf> (raw)
In-Reply-To: <20240807-tfa-src-update-v2-1-f2cd6166db5f@ti.com>

On Wed, 7 Aug 2024 12:48:19 -0500
Bryan Brattlof via buildroot <buildroot@buildroot.org> wrote:

> ARM_TRUSTED_FIRMWARE_SITE is currently pointing to the deprecated
> ARM-software github read-only mirror[0] which is no longer publishing
> new tags. They do have a newer github mirror under the TrustedFirmware-A
> organization[1] which continues to receive tag updates we could use
> however because of the way github generates tarballs changing the SITE
> to point to TrustedFormware-A changes the pre-calculated hash values
> for every version for everyone.
> 
> Without much way around changing all hash values if we want these latest
> tags, lets drop the github mirrors and move to the official git
> source[2] so we can download real tarballs which shouldn't change even
> if the ARM_TRUSTED_FIRMWARE_SITE moves again and hopefully preventing
> this from ever happening again.
> 
> [2] https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/
> [1] https://github.com/TrustedFirmware-A/trusted-firmware-a
> [0] https://github.com/ARM-software/arm-trusted-firmware
> 
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
>  .../fvp-ebbr/patches/arm-trusted-firmware/arm-trusted-firmware.hash   | 2 +-
>  .../patches/arm-trusted-firmware/arm-trusted-firmware.hash            | 2 +-
>  .../beagleplay/patches/arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
>  .../patches/arm-trusted-firmware/arm-trusted-firmware.hash            | 2 +-
>  .../patches/arm-trusted-firmware/arm-trusted-firmware.hash            | 2 +-
>  board/qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash     | 2 +-
>  .../stm32mp157/patches/arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
>  .../am62ax-sk/patches/arm-trusted-firmware/arm-trusted-firmware.hash  | 2 +-
>  .../am62x-sk/patches/arm-trusted-firmware/arm-trusted-firmware.hash   | 2 +-
>  .../am64x-sk/patches/arm-trusted-firmware/arm-trusted-firmware.hash   | 2 +-
>  boot/arm-trusted-firmware/arm-trusted-firmware.hash                   | 4 ++--
>  boot/arm-trusted-firmware/arm-trusted-firmware.mk                     | 3 ++-
>  12 files changed, 14 insertions(+), 13 deletions(-)

Applied to master, thanks! Note that your patch didn't apply as-is to
master, one defconfig had changed in the mean time. If possible make
sure to send patches that apply on the latest master.

I hope you didn't forgot any defconfig :-)

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

  reply	other threads:[~2024-08-07 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 17:48 [Buildroot] [PATCH v2 0/4] boot/arm-trusted-firmware: version bump and source update Bryan Brattlof via buildroot
2024-08-07 17:48 ` [Buildroot] [PATCH v2 1/4] boot/arm-trusted-firmware: move to official source for tf-a Bryan Brattlof via buildroot
2024-08-07 22:12   ` Thomas Petazzoni via buildroot [this message]
2024-08-08 16:39     ` Bryan Brattlof via buildroot
2024-08-07 17:48 ` [Buildroot] [PATCH v2 2/4] boot/arm-trusted-firmware: bump to v2.11 Bryan Brattlof via buildroot
2024-08-07 22:13   ` Thomas Petazzoni via buildroot
2024-08-07 17:48 ` [Buildroot] [PATCH v2 3/4] boot/arm-trusted-firmware: bump lts-v2.8 to v22.8.20 Bryan Brattlof via buildroot
2024-08-07 22:14   ` Thomas Petazzoni via buildroot
2024-08-07 17:48 ` [Buildroot] [PATCH v2 4/4] boot/arm-trusted-firmware: add lts-v2.10.x selection Bryan Brattlof via buildroot
2024-08-07 22:15   ` Thomas Petazzoni via buildroot

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=20240808001230.39ca2187@windsurf \
    --to=buildroot@buildroot.org \
    --cc=X15000177@gmail.com \
    --cc=ariel@vanguardiasur.com.ar \
    --cc=bb@ti.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=gadiyar@ti.com \
    --cc=geomatsi@gmail.com \
    --cc=marleen.vos@mind.be \
    --cc=michael@amarulasolutions.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vincent.stehle@arm.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