From: Peter Korsgaard <peter@korsgaard.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: buildroot@buildroot.org, thomas.petazzoni@bootlin.com
Subject: Re: [Buildroot] [PATCH] board/octavo: Add FORCE_CHECK_HASHES config and custom hashes
Date: Fri, 28 Feb 2025 14:53:31 +0100 [thread overview]
Message-ID: <87o6ymmazo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250227153358.526791-1-kory.maincent@bootlin.com> (Kory Maincent's message of "Thu, 27 Feb 2025 15:33:57 +0000")
>>>>> "Kory" == Kory Maincent <kory.maincent@bootlin.com> writes:
> Enable FORCE_CHECK_HASHES to ensure that all hashes are valid even
> from custom packages.
> Add custom version package hashes of Linux, U-boot and TF-A.
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-28 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 15:33 [Buildroot] [PATCH] board/octavo: Add FORCE_CHECK_HASHES config and custom hashes Kory Maincent via buildroot
2025-02-28 13:53 ` Peter Korsgaard [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=87o6ymmazo.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.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