From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Etienne Carriere <etienne.carriere@foss.st.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] configs/qemu_arm_vexpress_tz: bump tf-a and u-boot versions
Date: Tue, 23 Jul 2024 22:28:29 +0200 [thread overview]
Message-ID: <20240723222829.1526e8c3@windsurf> (raw)
In-Reply-To: <20240723163025.2733492-1-etienne.carriere@foss.st.com>
On Tue, 23 Jul 2024 18:30:24 +0200
Etienne Carriere <etienne.carriere@foss.st.com> wrote:
> Bump TF-A to version v2.10 and U-Boot to version v2024.07 for
> Qemu arm-vexpress/trustzone board config.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@foss.st.com>
> ---
> configs/qemu_arm_vexpress_tz_defconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks for the patch. However, are you sure you tested it? Indeed this
defconfig has BR2_DOWNLOAD_FORCE_CHECK_HASHES=y, which means all hashes
are checked. So when you bump components, it cannot be done without
updating hashes in board/qemu/patches/. Please note that those hash
files are shared by all qemu defconfigs. Could you check this?
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:[~2024-07-23 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 16:30 [Buildroot] [PATCH v2 1/2] configs/qemu_arm_vexpress_tz: bump tf-a and u-boot versions Etienne Carriere
2024-07-23 16:30 ` [Buildroot] [PATCH v2 2/2] board/qemu/arm-vexpress-tz: fix typos in readme file Etienne Carriere
2024-07-23 20:29 ` Thomas Petazzoni via buildroot
2024-08-31 16:56 ` Peter Korsgaard
2024-07-23 20:28 ` Thomas Petazzoni via buildroot [this message]
2024-07-24 9:57 ` [Buildroot] [PATCH v2 1/2] configs/qemu_arm_vexpress_tz: bump tf-a and u-boot versions Etienne CARRIERE - foss
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=20240723222829.1526e8c3@windsurf \
--to=buildroot@buildroot.org \
--cc=etienne.carriere@foss.st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox