From: Jarkko Sakkinen <jarkko@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Pankaj Gupta <pankaj.gupta@nxp.com>,
Horia Geanta <horia.geanta@nxp.com>,
Mimi Zohar <zohar@linux.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
James Bottomley <jejb@linux.ibm.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Jan Luebbe <j.luebbe@pengutronix.de>,
David Gstir <david@sigma-star.at>,
Eric Biggers <ebiggers@kernel.org>,
Richard Weinberger <richard@nod.at>,
Franck Lenormand <franck.lenormand@nxp.com>,
Sumit Garg <sumit.garg@linaro.org>,
Andreas Rammhold <andreas@rammhold.de>,
"tharvey@gateworks.com" <tharvey@gateworks.com>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
"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-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>
Subject: Re: [EXT] [PATCH v7 0/6] KEYS: trusted: Introduce support for NXP CAAM-based trusted keys
Date: Wed, 4 May 2022 07:11:16 +0300 [thread overview]
Message-ID: <YnH85FKdUN7DW8J8@kernel.org> (raw)
In-Reply-To: <73bb42fc-5d69-0c89-d42f-226a6d13248f@pengutronix.de>
On Thu, Apr 28, 2022 at 03:44:27PM +0200, Ahmad Fatoum wrote:
> Hello Pankaj,
>
> On 28.04.22 14:50, Pankaj Gupta wrote:
> > Hi Ahmad,
> >
> > I have tested the patch-set.
> > It is working as expected even when CAAM is compiled as kernel module.
> >
> > Reviewed-by: Pankaj Gupta <pankaj.gupta@nxp.com>
> > Tested-by: Pankaj Gupta <pankaj.gupta@nxp.com>
>
> Thanks for test and review. I have applied the tags on all patches
> in the series except the Tested-by for the last two. I think a Tested-by
> for maintainer and doc changes looks a bit odd. ^^
>
> I will incorporate Jarkko's documentation feedback and send a new series
> shortly.
Thank you for doing that (putting tags to correct place).
BR, Jarkko
next prev parent reply other threads:[~2022-05-04 4:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 20:56 [PATCH v7 0/6] KEYS: trusted: Introduce support for NXP CAAM-based trusted keys Ahmad Fatoum
2022-04-15 20:56 ` [PATCH v7 1/6] KEYS: trusted: allow use of TEE as backend without TCG_TPM support Ahmad Fatoum
2022-04-15 20:56 ` [PATCH v7 2/6] KEYS: trusted: allow use of kernel RNG for key material Ahmad Fatoum
2022-04-15 20:56 ` [PATCH v7 3/6] crypto: caam - add in-kernel interface for blob generator Ahmad Fatoum
2022-04-17 15:02 ` Jarkko Sakkinen
2022-04-17 18:47 ` Ahmad Fatoum
2022-04-15 20:56 ` [PATCH v7 4/6] KEYS: trusted: Introduce support for NXP CAAM-based trusted keys Ahmad Fatoum
2022-04-17 15:04 ` Jarkko Sakkinen
2022-04-15 20:56 ` [PATCH v7 5/6] doc: trusted-encrypted: describe new CAAM trust source Ahmad Fatoum
2022-04-15 20:56 ` [PATCH v7 6/6] MAINTAINERS: add myself as CAAM trusted key maintainer Ahmad Fatoum
2022-04-28 12:50 ` [EXT] [PATCH v7 0/6] KEYS: trusted: Introduce support for NXP CAAM-based trusted keys Pankaj Gupta
2022-04-28 13:44 ` Ahmad Fatoum
2022-05-04 4:11 ` Jarkko Sakkinen [this message]
2022-05-04 4:08 ` 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=YnH85FKdUN7DW8J8@kernel.org \
--to=jarkko@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=andreas@rammhold.de \
--cc=davem@davemloft.net \
--cc=david@sigma-star.at \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=franck.lenormand@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=j.luebbe@pengutronix.de \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=kernel@pengutronix.de \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=pankaj.gupta@nxp.com \
--cc=richard@nod.at \
--cc=s.trumtrar@pengutronix.de \
--cc=serge@hallyn.com \
--cc=sumit.garg@linaro.org \
--cc=tharvey@gateworks.com \
--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).