From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "David Gstir" <david@sigma-star.at>
Cc: "Mimi Zohar" <zohar@linux.ibm.com>,
"James Bottomley" <jejb@linux.ibm.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Kshitiz Varshney" <kshitiz.varshney@nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"dl-linux-imx" <linux-imx@nxp.com>,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"sigma star Kernel Team" <upstream+dcp@sigma-star.at>,
"David Howells" <dhowells@redhat.com>,
"Li Yang" <leoyang.li@nxp.com>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Tejun Heo" <tj@kernel.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"keyrings@vger.kernel.org" <keyrings@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"David Oberhollenzer" <david.oberhollenzer@sigma-star.at>,
"Varun Sethi" <V.Sethi@nxp.com>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>
Subject: Re: [EXT] [PATCH v8 6/6] docs: trusted-encrypted: add DCP as new trust source
Date: Sat, 04 May 2024 02:45:05 +0300 [thread overview]
Message-ID: <D10EQTNQXQYO.1QBNX5LMFU8NK@kernel.org> (raw)
In-Reply-To: <DB9357A7-0B20-4E57-AF66-3DD0F55ED538@sigma-star.at>
On Tue Apr 30, 2024 at 3:03 PM EEST, David Gstir wrote:
> Hi Jarkko,
>
> > On 30.04.2024, at 13:48, Kshitiz Varshney <kshitiz.varshney@nxp.com> wrote:
> >
> > Hi David,
> >
> >> -----Original Message-----
> >> From: David Gstir <david@sigma-star.at>
> >> Sent: Monday, April 29, 2024 5:05 PM
> >> To: Kshitiz Varshney <kshitiz.varshney@nxp.com>
>
>
> >>
> >> Did you get around to testing this?
> >> I’d greatly appreciate a Tested-by for this. :-)
> >>
> >> Thanks!
> >> BR, David
> >
> > Currently, I am bit busy with other priority activities. It will take time to test this patch set.
>
> How should we proceed here?
> Do we have to miss another release cycle, because of a Tested-by?
>
> If any bugs pop up I’ll happily fix them, but at the moment it appears to be more of a formality.
> IMHO the patch set itself is rather small and has been thoroughly reviewed to ensure that any huge
> issues would already have been caught by now.
I don't mind picking this actually since unless you consume it,
it should not get in the way. I'll pick it during the weekend.
Thanks for reminding.
BR, Jarkko
next prev parent reply other threads:[~2024-05-03 23: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 [this message]
2024-04-12 6:26 ` Herbert Xu
2024-04-13 21:44 ` Jarkko Sakkinen
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=D10EQTNQXQYO.1QBNX5LMFU8NK@kernel.org \
--to=jarkko@kernel.org \
--cc=V.Sethi@nxp.com \
--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=gaurav.jain@nxp.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=kshitiz.varshney@nxp.com \
--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=pankaj.gupta@nxp.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).