From: sashiko-bot@kernel.org
To: "Manuel Huber" <manuelh@nvidia.com>, "Fan Wu" <wufan@kernel.org>,
"David Howells" <dhowells@redhat.com>,
"Jarkko Sakkinen" <jarkko@kernel.org>
Cc: "Christian Brauner" <brauner@kernel.org>,
"Andrew Halaney" <andrew@amutable.com>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Luca Boccassi" <luca.boccassi@gmail.com>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-security-module@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v2 3/3] Documentation: ipe: document the IPE keyring
Date: Thu, 29 Oct 2026 00:37:45 +0000 [thread overview]
Message-ID: <sashiko-outbox-188573@kernel.org> (raw)
In-Reply-To: <20261029-b4-ipe-keyring-rfc-v2-3-77727b205844@nvidia.com>
> From: Manuel Huber <manuelh@nvidia.com>
>
> Document the .ipe policy-verification keyring with its additive use
> after the existing trust sources and the userspace's role in
> sustaining trust. Mention requirements for maintaining policy trust
> in kexec scenarios.
>
> Signed-off-by: Manuel Huber <manuelh@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029-b4-ipe-keyring-rfc-v2-0-77727b205844@nvidia.com?part=3
prev parent reply other threads:[~2026-10-29 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 0:30 [PATCH v2 0/3] IPE: add a dedicated policy keyring Manuel Huber via B4 Relay
2026-10-29 0:30 ` [PATCH v2 1/3] ipe: add the .ipe " Manuel Huber via B4 Relay
2026-10-29 0:50 ` sashiko-bot
2026-10-29 0:30 ` [PATCH v2 2/3] keys: add KEY_SPEC_IPE_KEYRING Manuel Huber via B4 Relay
2026-10-29 0:50 ` sashiko-bot
2026-10-29 0:30 ` [PATCH v2 3/3] Documentation: ipe: document the IPE keyring Manuel Huber via B4 Relay
2026-10-29 0:37 ` sashiko-bot [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=sashiko-outbox-188573@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew@amutable.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=kexec@lists.infradead.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luca.boccassi@gmail.com \
--cc=manuelh@nvidia.com \
--cc=paul@paul-moore.com \
--cc=rdunlap@infradead.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=wufan@kernel.org \
/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