From: "Claudius Heine" <ch@denx.de>
To: "Cetin, Gokhan" <gokhan.cetin@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Cc: "quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>,
"Heinisch, Alexander" <alexander.heinisch@siemens.com>
Subject: Re: [PATCH v6 0/4] initramfs-crypt-hook patch
Date: Mon, 16 Jun 2025 11:35:57 +0200 [thread overview]
Message-ID: <DANUTHR0IO7T.1O5DQWLF91XHA@denx.de> (raw)
In-Reply-To: <PRAPR10MB542211966641957AF9AD3C788075A@PRAPR10MB5422.EURPRD10.PROD.OUTLOOK.COM>
Hi Gokhan,
On Wed Jun 11, 2025 at 10:46 PM CEST, Gokhan Cetin wrote:
> Hi,
>
> One feedback from my side:
> `tpm2_createpolicy` is still used by the `clevis` backend and should be part of the HOOK_COPY_EXECS, that patch 1/4 removes it.
> Probably overlooked because it has no direct use in the encrypt_partition script.
Good catch. Done in v7.
kind regards,
Claudius
>
> Regards,
> Gokhan
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2025-06-16 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 7:43 [PATCH v6 0/4] initramfs-crypt-hook patch Claudius Heine
2025-03-20 7:43 ` [PATCH v6 1/4] initramfs-crypt-hook: store initial encryption key in TPM2 Claudius Heine
2025-03-20 7:43 ` [PATCH v6 2/4] initramfs-crypt-hook: add re-encryption recovery Claudius Heine
2025-03-20 7:43 ` [PATCH v6 3/4] initramfs-crypt-hook: implement 'noencrypt' option Claudius Heine
2025-03-20 7:43 ` [PATCH v6 4/4] initramfs-crypt-hook: add 'format-if-empty' feature Claudius Heine
2025-05-30 14:19 ` [PATCH v6 0/4] initramfs-crypt-hook patch Jan Kiszka
2025-06-02 8:20 ` Claudius Heine
2025-06-02 8:24 ` Jan Kiszka
2025-06-11 20:46 ` Cetin, Gokhan
2025-06-16 9:35 ` Claudius Heine [this message]
2025-06-16 11:11 ` Jan Kiszka
2025-06-16 11:58 ` Jan Kiszka
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=DANUTHR0IO7T.1O5DQWLF91XHA@denx.de \
--to=ch@denx.de \
--cc=alexander.heinisch@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=gokhan.cetin@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.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