From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] board/ti/am6{2, 4}x: add missing uboot.hash file
Date: Mon, 06 May 2024 12:51:19 +0200 [thread overview]
Message-ID: <8734qv2oyg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240410214454.86748-3-romain.naour@smile.fr> (Romain Naour's message of "Wed, 10 Apr 2024 23:44:54 +0200")
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
> Arnout noticed during the review that uboot.hash was missing from
> BR2_GLOBAL_PATCH_DIR.
> "The hash for 2024.01 is currently in boot/uboot/uboot.hash, but as soon as we
> update the U-Boot version, it will no longer be. So to be future safe, we should
> add a local override of the uboot hash file as well (which is simply identical
> to uboot.hash)."
> This is required since BR2_DOWNLOAD_FORCE_CHECK_HASHES is now enabled.
> [1] http://lists.busybox.net/pipermail/buildroot/2024-April/689283.html
> Reported-by: Arnout Vandecappelle <arnout@mind.be>
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-06 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 21:44 [Buildroot] [PATCH 1/3] boot/uboot: remove BR2_TARGET_UBOOT_NEEDS_TI_K3_BOOT_FIRMWARE Romain Naour
2024-04-10 21:44 ` [Buildroot] [PATCH 2/3] boot/{uboot, ti-k3-r5-loader}: remove uneeded python-jsonschema dependency Romain Naour
2024-05-06 10:51 ` Peter Korsgaard
2024-04-10 21:44 ` [Buildroot] [PATCH 3/3] board/ti/am6{2, 4}x: add missing uboot.hash file Romain Naour
2024-05-06 10:51 ` Peter Korsgaard [this message]
2024-05-06 10:51 ` [Buildroot] [PATCH 1/3] boot/uboot: remove BR2_TARGET_UBOOT_NEEDS_TI_K3_BOOT_FIRMWARE Peter Korsgaard
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=8734qv2oyg.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
/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.