From: Mario Limonciello <superm1@kernel.org>
To: mario.limonciello@amd.com, davem@davemloft.net,
Herbert Xu <herbert@gondor.apana.org.au>,
john.allen@amd.com, thomas.lendacky@amd.com
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH 0/2] Add some missing info registers
Date: Sat, 17 May 2025 15:26:28 -0500 [thread overview]
Message-ID: <20250517202657.2044530-1-superm1@kernel.org> (raw)
From: Mario Limonciello <mario.limonciello@amd.com>
pspv5 and teev2 are missing the registers for version
information.
Mario Limonciello (2):
crypto: ccp - Add missing bootloader info reg for pspv5
crypto: ccp - Add missing tee info reg for teev2
drivers/crypto/ccp/sp-pci.c | 2 ++
1 file changed, 2 insertions(+)
--
2.43.0
next reply other threads:[~2025-05-17 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:26 Mario Limonciello [this message]
2025-05-17 20:26 ` [PATCH 1/2] crypto: ccp - Add missing bootloader info reg for pspv5 Mario Limonciello
2025-05-17 20:26 ` [PATCH 2/2] crypto: ccp - Add missing tee info reg for teev2 Mario Limonciello
2025-05-19 6:03 ` [PATCH 0/2] Add some missing info registers Herbert Xu
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=20250517202657.2044530-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=thomas.lendacky@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