From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Cc: David Gstir <david@sigma-star.at>,
linux-doc@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Mimi Zohar <zohar@linux.ibm.com>,
David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
Paul Moore <paul@paul-moore.com>,
Jonathan Corbet <corbet@lwn.net>,
Richard Weinberger <richard@nod.at>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
James Morris <jmorris@namei.org>,
NXP Linux Team <linux-imx@nxp.com>,
James Bottomley <jejb@linux.ibm.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
sigma star Kernel Team <upstream+dcp@sigma-star.at>,
"Steven Rostedt \(Google\)" <rostedt@goodmis.org>,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
linux-security-module@vger.kernel.org,
linux-crypto@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Tejun Heo <tj@kernel.org>,
linux-integrity@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v8 6/6] docs: trusted-encrypted: add DCP as new trust source
Date: Sun, 14 Apr 2024 00:44:20 +0300 [thread overview]
Message-ID: <D0JBNGXAUBLT.1HW29NDQUKW72@kernel.org> (raw)
In-Reply-To: <ZhjUH3TZ99cT3Rhq@gondor.apana.org.au>
On Fri Apr 12, 2024 at 9:26 AM EEST, Herbert Xu wrote:
> On Wed, Apr 03, 2024 at 06:47:51PM +0300, Jarkko Sakkinen wrote:
> >
> > Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> >
> > I can only test that this does not break a machine without the
> > hardware feature.
>
> Please feel free to take this through your tree.
>
> Thanks,
OK, thanks!
BR, Jarkko
prev parent reply other threads:[~2024-04-13 21:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 7:21 [PATCH v8 0/6] DCP as trusted keys backend David Gstir
2024-04-03 7:21 ` [PATCH v8 1/6] crypto: mxs-dcp: Add support for hardware-bound keys David Gstir
2024-04-03 7:21 ` [PATCH v8 2/6] KEYS: trusted: improve scalability of trust source config David Gstir
2024-04-03 7:21 ` [PATCH v8 3/6] KEYS: trusted: Introduce NXP DCP-backed trusted keys David Gstir
2024-04-09 10:54 ` [EXT] " Kshitiz Varshney
2024-04-09 17:27 ` Ahmad Fatoum
2024-04-10 7:13 ` Kshitiz Varshney
2024-04-03 7:21 ` [PATCH v8 4/6] MAINTAINERS: add entry for DCP-based " David Gstir
2024-04-03 7:21 ` [PATCH v8 5/6] docs: document DCP-backed trusted keys kernel params David Gstir
2024-04-03 7:21 ` [PATCH v8 6/6] docs: trusted-encrypted: add DCP as new trust source David Gstir
2024-04-03 13:24 ` Bagas Sanjaya
2024-04-03 15:47 ` Jarkko Sakkinen
2024-04-09 9:48 ` [EXT] " Kshitiz Varshney
[not found] ` < <DB6PR04MB3190F6B78FF3760EBCC14E758F072@DB6PR04MB3190.eurprd04.prod.outlook.com>
2024-04-13 21:24 ` Jarkko Sakkinen
2024-04-29 11:35 ` [EXT] " David Gstir
2024-04-30 11:48 ` Kshitiz Varshney
2024-04-30 12:03 ` David Gstir
2024-05-03 23:45 ` Jarkko Sakkinen
2024-04-12 6:26 ` Herbert Xu
2024-04-13 21:44 ` Jarkko Sakkinen [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=D0JBNGXAUBLT.1HW29NDQUKW72@kernel.org \
--to=jarkko@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=david.oberhollenzer@sigma-star.at \
--cc=david@sigma-star.at \
--cc=dhowells@redhat.com \
--cc=festevam@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=kernel@pengutronix.de \
--cc=keyrings@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paul@paul-moore.com \
--cc=paulmck@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=s.hauer@pengutronix.de \
--cc=serge@hallyn.com \
--cc=shawnguo@kernel.org \
--cc=tj@kernel.org \
--cc=upstream+dcp@sigma-star.at \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).