From: Tom Lendacky <thomas.lendacky@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>
Cc: open list <linux-kernel@vger.kernel.org>,
"open list:AMD CRYPTOGRAPHIC COPROCESSOR (CCP) DRIVER"
<linux-crypto@vger.kernel.org>,
Kerneis Gabriel <Gabriel.Kerneis@ssi.gouv.fr>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [PATCH v2 1/4] crypto: ccp: cache capability into psp device
Date: Thu, 31 Mar 2022 15:02:57 -0500 [thread overview]
Message-ID: <fef8a6d1-8491-c62e-c718-299d0063ddd8@amd.com> (raw)
In-Reply-To: <20220329164117.1449-2-mario.limonciello@amd.com>
On 3/29/22 11:41, Mario Limonciello wrote:
> The results of the capability register will be used by future
> code at runtime rather than just initialization.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> drivers/crypto/ccp/psp-dev.c | 37 +++++++++++++++++-------------------
> drivers/crypto/ccp/psp-dev.h | 5 +++++
> 2 files changed, 22 insertions(+), 20 deletions(-)
>
next prev parent reply other threads:[~2022-03-31 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 16:41 [PATCH v2 0/4] Export PSP security attributes Mario Limonciello
2022-03-29 16:41 ` [PATCH v2 1/4] crypto: ccp: cache capability into psp device Mario Limonciello
2022-03-31 20:02 ` Tom Lendacky [this message]
2022-03-29 16:41 ` [PATCH v2 2/4] crypto: ccp: Export PSP security bits to userspace Mario Limonciello
2022-03-31 20:03 ` Tom Lendacky
2022-03-29 16:41 ` [PATCH v2 3/4] crypto: ccp: Allow PSP driver to load without SEV/TEE support Mario Limonciello
2022-03-31 20:10 ` Tom Lendacky
2022-03-29 16:41 ` [PATCH v2 4/4] crypto: ccp: When TSME and SME both detected notify user Mario Limonciello
2022-03-31 20:12 ` Tom Lendacky
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=fef8a6d1-8491-c62e-c718-299d0063ddd8@amd.com \
--to=thomas.lendacky@amd.com \
--cc=Gabriel.Kerneis@ssi.gouv.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hughsient@gmail.com \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.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
all inboxes | Powered by JetHome®