From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Stefan Kerkmann <s.kerkmann@pengutronix.de>
Subject: Re: [PATCH] hab: writing the same srk hash is not an error
Date: Tue, 05 Aug 2025 11:23:42 +0200 [thread overview]
Message-ID: <175438582243.3509922.730367748623284066.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250709-fix-hab-equal-hash-writes-v1-1-6a59bb4b5ff1@pengutronix.de>
On Wed, 09 Jul 2025 09:42:43 +0200, Stefan Kerkmann wrote:
> Before this commit writing the same srk hash twice failed with an error.
> This is inconsistent with other invocations of the hab tool e.g.: `hab
> -l -p` doesn't fail if the lockdown bit is already set.
>
> So let's align the behavior by only throwing an error if we attempt to
> write a srk hash that is different from the one that is already burned.
>
> [...]
Applied, thanks!
[1/1] hab: writing the same srk hash is not an error
https://git.pengutronix.de/cgit/barebox/commit/?id=788757cf85d2 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-08-05 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 7:42 Stefan Kerkmann
2025-07-14 7:24 ` Ahmad Fatoum
2025-08-05 9:23 ` Sascha Hauer [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=175438582243.3509922.730367748623284066.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.kerkmann@pengutronix.de \
/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