From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] board/qemu/patches/arm-trusted-firmware: add v2.10 hash
Date: Fri, 23 Aug 2024 17:53:17 +0200 [thread overview]
Message-ID: <20240823175317.7e58f2c6@windsurf> (raw)
In-Reply-To: <20240823075600.1440000-1-peter@korsgaard.com>
On Fri, 23 Aug 2024 09:56:00 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes https://gitlab.com/buildroot.org/buildroot/-/jobs/7644930127
> ERROR: No hash found for arm-trusted-firmware-v2.10-git4.tar.gz
>
> Commit d037d9c2d63e9cd47b (configs/qemu: Update defconfigs to Linux 6.6.32)
> enabled BR2_DOWNLOAD_FORCE_CHECK_HASHES, but forgot to take into
> consideration that qemu_aarch64_ebbr_defconfig uses arm-trusted-firmware
> v2.10 since commit 73813c56c8bb (configs/qemu_{arm, aarch64}_ebbr: bump
> Linux, U-Boot and TF-A).
>
> Add the hash to fix the build.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> .../qemu/patches/arm-trusted-firmware/arm-trusted-firmware.hash | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, 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
prev parent reply other threads:[~2024-08-23 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 7:56 [Buildroot] [PATCH] board/qemu/patches/arm-trusted-firmware: add v2.10 hash Peter Korsgaard
2024-08-23 15:53 ` Thomas Petazzoni via buildroot [this message]
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=20240823175317.7e58f2c6@windsurf \
--to=buildroot@buildroot.org \
--cc=peter@korsgaard.com \
--cc=romain.naour@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.