From: Tom Lendacky <thomas.lendacky@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: "open list:AMD CRYPTOGRAPHIC COPROCESSOR (CCP) DRIVER - DB..."
<linux-crypto@vger.kernel.org>,
Richard Hughes <hughsient@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] crypto: ccp: Move security attributes to their own file
Date: Tue, 28 May 2024 10:30:21 -0500 [thread overview]
Message-ID: <f64b1dc0-a2a3-3df6-b1aa-d98452a5996d@amd.com> (raw)
In-Reply-To: <20240527152649.3722-3-mario.limonciello@amd.com>
On 5/27/24 10:26, Mario Limonciello wrote:
> To prepare for other code that will manipulate security attributes
> move the handling code out of sp-pci.c. No intended functional changes.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
next prev parent reply other threads:[~2024-05-28 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 15:26 [PATCH 0/5] Enable PSP security attributes on more SoCs Mario Limonciello
2024-05-27 15:26 ` [PATCH 1/5] crypto: ccp: Represent capabilities register as a union Mario Limonciello
2024-05-28 15:30 ` Tom Lendacky
2024-05-27 15:26 ` [PATCH 2/5] crypto: ccp: Move security attributes to their own file Mario Limonciello
2024-05-28 15:30 ` Tom Lendacky [this message]
2024-05-28 20:13 ` kernel test robot
2024-05-27 15:26 ` [PATCH 3/5] crypto: ccp: align psp_platform_access_msg Mario Limonciello
2024-05-28 15:30 ` Tom Lendacky
2024-05-27 15:26 ` [PATCH 4/5] crypto: ccp: Add support for getting security attributes on some older systems Mario Limonciello
2024-05-28 15:28 ` Tom Lendacky
2024-05-27 15:26 ` [PATCH 5/5] crypto: ccp: Move message about TSME being enabled later in init Mario Limonciello
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=f64b1dc0-a2a3-3df6-b1aa-d98452a5996d@amd.com \
--to=thomas.lendacky@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=hughsient@gmail.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®