From: Bryan Brattlof via buildroot <buildroot@buildroot.org>
To: <buildroot@buildroot.org>
Cc: "Vincent Stehlé" <vincent.stehle@arm.com>,
"Marleen Vos" <marleen.vos@mind.be>,
"Michael Trimarchi" <michael@amarulasolutions.com>,
"Sergey Matyukevich" <geomatsi@gmail.com>,
"Bryan Brattlof" <bb@ti.com>, "Xuanhao Shi" <X15000177@gmail.com>,
"Ariel D'Alessandro" <ariel@vanguardiasur.com.ar>,
"Romain Naour" <romain.naour@gmail.com>,
"Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
"Anand Gadiyar" <gadiyar@ti.com>
Subject: [Buildroot] [PATCH 0/3] boot/arm-trusted-firmware: version bump and source update
Date: Mon, 22 Jul 2024 14:17:36 -0500 [thread overview]
Message-ID: <20240722-tfa-src-update-v1-0-e68bba62f146@ti.com> (raw)
Hello everyone,
When trying to bump the versions for arm-trusted-firmware I noticed
we're using the old mirror which hasn't received any new tags in a
while. So this changes ARM_TRUSTED_FIRMWARE_SITE to point to the new
TrustedFirmware-A[0] organization and updates all the hashes I could see
I did notice the lts-v2.10.x branch however I didn't add it as I didn't
see anyone using it. (The boards using TI's K3 SoCs will be going to
v2.11 in another patch series)
Happy reviewing
~Bryan
[0] https://github.com/TrustedFirmware-A
Signed-off-by: Bryan Brattlof <bb@ti.com>
---
Bryan Brattlof (3):
boot/arm-trusted-firmware: update source to the new mirror
boot/arm-trusted-firmware: bump to v2.11
boot/arm-trusted-firmware: bump latest v2.8 version
.../fvp-ebbr/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 +-
.../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 +-
.../patches/arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
.../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/Config.in | 6 +++---
boot/arm-trusted-firmware/arm-trusted-firmware.hash | 4 ++--
boot/arm-trusted-firmware/arm-trusted-firmware.mk | 2 +-
.../0001-build-tools-avoid-unnecessary-link.patch | 0
14 files changed, 16 insertions(+), 16 deletions(-)
---
base-commit: 4e4554eeb76e8b516c6cbcd66f15868492aac594
change-id: 20240623-tfa-src-update-8de4cdf5ceed
Best regards,
--
Bryan Brattlof <bb@ti.com>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-07-22 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 19:17 Bryan Brattlof via buildroot [this message]
2024-07-22 19:17 ` [Buildroot] [PATCH 1/3] boot/arm-trusted-firmware: update source to the new mirror Bryan Brattlof via buildroot
2024-08-03 21:59 ` Thomas Petazzoni via buildroot
2024-08-04 0:52 ` Bryan Brattlof via buildroot
2024-07-22 19:17 ` [Buildroot] [PATCH 2/3] boot/arm-trusted-firmware: bump to v2.11 Bryan Brattlof via buildroot
2024-07-22 19:17 ` [Buildroot] [PATCH 3/3] boot/arm-trusted-firmware: bump latest v2.8 version Bryan Brattlof 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=20240722-tfa-src-update-v1-0-e68bba62f146@ti.com \
--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=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