From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org, Bartosz Bilas <b.bilas@grinn-global.com>,
Marleen Vos <marleen.vos@mind.be>,
Raphael Gallais-Pou <rgallaispou@gmail.com>,
linux-amarula@amarulasolutions.com
Subject: Re: [Buildroot] [PATCH v4 1/2] configs/stm32mp135f_dk: fix optee hash
Date: Sat, 19 Apr 2025 18:36:33 +0200 [thread overview]
Message-ID: <20250419183633.788bab43@windsurf> (raw)
In-Reply-To: <20250413164708.1943803-1-dario.binacchi@amarulasolutions.com>
On Sun, 13 Apr 2025 18:47:07 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> 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>
>
> ---
Both applied, thanks!
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
next prev parent reply other threads:[~2025-04-19 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 16:47 [Buildroot] [PATCH v4 1/2] configs/stm32mp135f_dk: fix optee hash Dario Binacchi
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 [this message]
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=20250419183633.788bab43@windsurf \
--to=buildroot@buildroot.org \
--cc=b.bilas@grinn-global.com \
--cc=dario.binacchi@amarulasolutions.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.