From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marleen Vos via buildroot <buildroot@buildroot.org>
Cc: Marleen Vos <marleen.vos@mind.be>, marleen.vos@essensium.com
Subject: Re: [Buildroot] [PATCH 4/7] boot/arm-trusted-firmware: add config option to use latest lts-v2.8.13
Date: Tue, 6 Feb 2024 17:38:01 +0100 [thread overview]
Message-ID: <20240206173801.02d805c1@windsurf> (raw)
In-Reply-To: <20231219121508.1695768-5-marleen.vos@mind.be>
Hello Marleen,
On Tue, 19 Dec 2023 13:15:05 +0100
Marleen Vos via buildroot <buildroot@buildroot.org> wrote:
> From: Marleen Vos <marleen.vos@mind.be>
>
> Patch 0001-feat-build-add-support-for-new-binutils-versions.patch as
> found in v2.8 patch dir has already been applied in lts-v2.8.13
> Patch 0002-build-tools-avoid-unnecessary-link.patch from v2.8 has
> been included as 0001-build-tools-avoid-unnecessary-link.patch for
> lts-v2.8.13
>
> Signed-off-by: Marleen Vos <marleen.vos@mind.be>
Thanks for the good arguments from Arnout, we got convinced and applied
your patch to master, with a few changes, see below.
> +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_LATEST_LTS_v2_8_VERSION
^^^ we dropped the "v" from here
> sha256 327c65b1bc231608a7a808b068b00c1a22310e9fc86158813cd10a9711d5725e arm-trusted-firmware-v2.7.tar.gz
> +sha256 e55ae7105c996b60f748b2eb6adeaf5ac8946425e1d4294ecc1c56aebf435274 trusted-firmware-a-lts-v2.8.13.tar.gz
We were surprised by the files having different base names here. Turns
out the hash of trusted-firmware-a-lts-v2.8.13.tar.gz was in fact never
checked, which is why you didn't release that
trusted-firmware-a-lts-v2.8.13.tar.gz was an incorrect file name. So we
added a preliminary commit to make sure that this hash will be checked,
and fixed the file name.
See:
https://gitlab.com/buildroot.org/buildroot/-/commit/c6ab9328e13c6c9a1538b4a33824525a990b623d
https://gitlab.com/buildroot.org/buildroot/-/commit/2a310666e06c9c5edd6879d32295c63b7851c817
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-06 16:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 12:15 [Buildroot] [PATCH 0/7] Updates for boards based on stm32mp157, related to arm-trusted-firmware Marleen Vos via buildroot
2023-12-19 12:15 ` [Buildroot] [PATCH 1/7] DEVELOPERS: added marleen.vos@mind.be for boards/configs based on stm32mp15 Marleen Vos via buildroot
2024-02-06 13:23 ` Thomas Petazzoni via buildroot
2023-12-19 12:15 ` [Buildroot] [PATCH 2/7] board/stmicroelectronics: generalise BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES regex Marleen Vos via buildroot
2024-02-06 13:23 ` Thomas Petazzoni via buildroot
2023-12-19 12:15 ` [Buildroot] [PATCH 3/7] configs/stm32mp157*: bump ATF to v2.6 Marleen Vos via buildroot
2024-02-06 13:23 ` Thomas Petazzoni via buildroot
2023-12-19 12:15 ` [Buildroot] [PATCH 4/7] boot/arm-trusted-firmware: add config option to use latest lts-v2.8.13 Marleen Vos via buildroot
2024-02-06 13:25 ` Thomas Petazzoni via buildroot
2024-02-06 13:38 ` Arnout Vandecappelle via buildroot
2024-02-06 13:39 ` Thomas Petazzoni via buildroot
2024-02-06 13:59 ` Arnout Vandecappelle via buildroot
2024-02-06 16:38 ` Thomas Petazzoni via buildroot [this message]
2023-12-19 12:15 ` [Buildroot] [PATCH 5/7] configs/stm32mp157a_dk1_defconfig: update arm-trusted-firmware to lts-v2.8.13 Marleen Vos via buildroot
2024-02-06 16:38 ` Thomas Petazzoni via buildroot
2023-12-19 12:15 ` [Buildroot] [PATCH 6/7] configs/stm32mp157c_dk2_defconfig: " Marleen Vos via buildroot
2024-02-06 16:38 ` Thomas Petazzoni via buildroot
2023-12-19 12:15 ` [Buildroot] [PATCH 7/7] boot/arm-trusted-firmware: bump latest version to v2.10 Marleen Vos via buildroot
2024-02-06 13:39 ` Thomas Petazzoni 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=20240206173801.02d805c1@windsurf \
--to=buildroot@buildroot.org \
--cc=marleen.vos@essensium.com \
--cc=marleen.vos@mind.be \
--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