From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
dmitrii.omelchenko@cloud.ionos.com,
Jack Wang <jinpu.wang@cloud.ionos.com>,
Jack Wang <jinpu.wang@ionos.com>
Subject: Re: [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes
Date: Fri, 14 Aug 2026 22:33:15 -0400 [thread overview]
Message-ID: <20260814193000.15@kernel.org> (raw)
In-Reply-To: <20260814100652.225499-1-jinpu.wang@ionos.com>
> Patches 1-2 are the missing dependencies of commit 3f8f0133a5fc
> ("crypto: ccp - Move SEV/SNP Platform initialization to KVM"), already
> queued as of 6.12.97 (bb1c8464702540 on queue/6.12). That commit
> dropped SEV/SNP platform init from the CCP driver's probe path,
> expecting KVM to take over, but the counterpart commits that give KVM
> that responsibility were never queued alongside it.
Queued the series for 6.12, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-08-15 2:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 10:02 [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes Jack Wang
2026-08-14 10:02 ` [stable-6.12 1/4] crypto: ccp - Add new SEV/SNP platform shutdown API Jack Wang
2026-08-14 10:02 ` [stable-6.12 2/4] KVM: SVM: Add support to initialize SEV/SNP functionality in KVM Jack Wang
2026-08-14 14:40 ` Sean Christopherson
2026-08-14 10:02 ` [stable-6.12 3/4] crypto: ccp - Fix checks for SNP_VLEK_LOAD input buffer length Jack Wang
2026-08-14 10:02 ` [stable-6.12 4/4] crypto: ccp - Abort doing SEV INIT if SNP INIT fails Jack Wang
2026-08-15 2:33 ` Sasha Levin [this message]
2026-08-17 4:51 ` [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes Jinpu Wang
2026-08-17 5:00 ` Greg KH
2026-08-17 5:22 ` Jinpu Wang
2026-08-17 5:34 ` Greg KH
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=20260814193000.15@kernel.org \
--to=sashal@kernel.org \
--cc=dmitrii.omelchenko@cloud.ionos.com \
--cc=gregkh@linuxfoundation.org \
--cc=jinpu.wang@cloud.ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=stable@vger.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