From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] Dockerfile: Update to a more current TF-A release tag
Date: Tue, 8 Apr 2025 14:21:40 -0600 [thread overview]
Message-ID: <20250408202141.1434754-1-trini@konsulko.com> (raw)
In preparation for using TF-A more in our CI loops, switch to the
current release tag for TF-A.
Signed-off-by: Tom Rini <trini@konsulko.com>
---
tools/docker/Dockerfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index e14d1640f9cd..3b0c403618a8 100644
--- a/tools/docker/Dockerfile
+++ b/tools/docker/Dockerfile
@@ -230,7 +230,7 @@ RUN git clone https://gitlab.com/qemu-project/qemu.git /tmp/qemu && \
# Build fiptool
RUN git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git /tmp/tf-a && \
cd /tmp/tf-a/ && \
- git checkout v2.10.0 && \
+ git checkout v2.12.0 && \
cd tools/fiptool && \
make -j$(nproc) && \
mkdir -p /usr/local/bin && \
--
2.43.0
next reply other threads:[~2025-04-08 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 20:21 Tom Rini [this message]
2025-04-08 20:21 ` [PATCH 2/2] Dockerfile: Download the Arm FVP and extract it Tom Rini
2025-04-10 17:33 ` [PATCH 1/2] Dockerfile: Update to a more current TF-A release tag Tom Rini
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=20250408202141.1434754-1-trini@konsulko.com \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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