From: Dario Binacchi <dario.binacchi@amarulasolutions.com>
To: buildroot@buildroot.org
Cc: Bartosz Bilas <b.bilas@grinn-global.com>,
Marleen Vos <marleen.vos@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Raphael Gallais-Pou <rgallaispou@gmail.com>,
linux-amarula@amarulasolutions.com,
Dario Binacchi <dario.binacchi@amarulasolutions.com>
Subject: [Buildroot] [PATCH v4 1/2] configs/stm32mp135f_dk: fix optee hash
Date: Sun, 13 Apr 2025 18:47:07 +0200 [thread overview]
Message-ID: <20250413164708.1943803-1-dario.binacchi@amarulasolutions.com> (raw)
The build command:
make stm32mp135f_dk_defconfig
fails with the errors:
ERROR: No hash found for optee-client-4.3.0.tar.gz
ERROR: No hash found for optee-os-4.3.0.tar.gz
Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/9690369624
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
---
Changes v3 -> v4:
- Add Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/9690369624
in the commit message
Changes v2 -> v3:
- Added in v3
.../common/stm32mp1xx/patches/optee-client/optee-client.hash | 2 ++
.../common/stm32mp1xx/patches/optee-os/optee-os.hash | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
create mode 100644 board/stmicroelectronics/common/stm32mp1xx/patches/optee-client/optee-client.hash
diff --git a/board/stmicroelectronics/common/stm32mp1xx/patches/optee-client/optee-client.hash b/board/stmicroelectronics/common/stm32mp1xx/patches/optee-client/optee-client.hash
new file mode 100644
index 000000000000..5423bf93a580
--- /dev/null
+++ b/board/stmicroelectronics/common/stm32mp1xx/patches/optee-client/optee-client.hash
@@ -0,0 +1,2 @@
+# Locally calculated
+sha256 a9a91bdb433df795c87a6d15198effbd648e3671ae611f2a3f8b41229d61cce0 optee-client-4.3.0.tar.gz
diff --git a/board/stmicroelectronics/common/stm32mp1xx/patches/optee-os/optee-os.hash b/board/stmicroelectronics/common/stm32mp1xx/patches/optee-os/optee-os.hash
index 73d4e2c4dafb..2e12a5cdea78 100644
--- a/board/stmicroelectronics/common/stm32mp1xx/patches/optee-os/optee-os.hash
+++ b/board/stmicroelectronics/common/stm32mp1xx/patches/optee-os/optee-os.hash
@@ -1,2 +1,2 @@
# Locally calculated
-sha256 03b91fd7dfdf890e3966f931f07634a2b6a2911bbee2a02ecc48d4a40cf6a9b8 optee-os-4.3.0-git4.tar.gz
+sha256 390b271905c828d6def9fa6a77bbaa425f3b434d733c8eb18f582ccbc6896096 optee-os-4.3.0.tar.gz
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-04-13 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 16:47 Dario Binacchi [this message]
2025-04-13 16:47 ` [Buildroot] [PATCH v4 2/2] configs/stm32mp1*_dk*: bump TF-A to 2.10, Linux to 6.12.22 and U-Boot to 2025.04 Dario Binacchi
2025-04-14 18:16 ` Raphaël Gallais-Pou
2025-04-14 18:15 ` [Buildroot] [PATCH v4 1/2] configs/stm32mp135f_dk: fix optee hash Raphaël Gallais-Pou
2025-04-19 16:36 ` Thomas Petazzoni via buildroot
2025-05-02 10:43 ` Arnout Vandecappelle 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=20250413164708.1943803-1-dario.binacchi@amarulasolutions.com \
--to=dario.binacchi@amarulasolutions.com \
--cc=b.bilas@grinn-global.com \
--cc=buildroot@buildroot.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=marleen.vos@mind.be \
--cc=rgallaispou@gmail.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