From: Alexey Kardashevskiy <aik@amd.com>
To: <linux-crypto@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Ashish Kalra <ashish.kalra@amd.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
John Allen <john.allen@amd.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Dan Williams <dan.j.williams@intel.com>,
Alexey Kardashevskiy <aik@amd.com>, <x86@kernel.org>,
<linux-coco@lists.linux.dev>,
"Pratik R . Sampat" <prsampat@amd.com>
Subject: [PATCH kernel 0/2] crypto/ccp: Fixes for PCI IDE
Date: Fri, 23 Jan 2026 16:30:55 +1100 [thread overview]
Message-ID: <20260123053057.1350569-1-aik@amd.com> (raw)
A couple of fixes for bugs discovered recently as we got more of
these devices and tested more configurations with multiple devices
on same and different bridges.
This is based on sha1
0499add8efd7 Paolo Bonzini Merge tag 'kvm-x86-fixes-6.19-rc1' of htts://github.com/kvm-x86/linux into HEAD
Please comment. Thanks.
Alexey Kardashevskiy (2):
crypto/ccp: Use PCI bridge defaults for IDE
crypto/ccp: Allow multiple streams on the same root bridge
drivers/crypto/ccp/sev-dev-tsm.c | 15 +--------------
1 file changed, 1 insertion(+), 14 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-23 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 5:30 Alexey Kardashevskiy [this message]
2026-01-23 5:30 ` [PATCH kernel 1/2] crypto/ccp: Use PCI bridge defaults for IDE Alexey Kardashevskiy
2026-01-23 22:48 ` dan.j.williams
2026-01-23 5:30 ` [PATCH kernel 2/2] crypto/ccp: Allow multiple streams on the same root bridge Alexey Kardashevskiy
2026-01-23 22:59 ` dan.j.williams
2026-01-26 0:44 ` Alexey Kardashevskiy
2026-01-27 6:59 ` dan.j.williams
2026-01-29 22:29 ` Alexey Kardashevskiy
2026-01-23 16:01 ` [PATCH kernel 0/2] crypto/ccp: Fixes for PCI IDE 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=20260123053057.1350569-1-aik@amd.com \
--to=aik@amd.com \
--cc=ashish.kalra@amd.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prsampat@amd.com \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/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