Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jinpu Wang <jinpu.wang@cloud.ionos.com>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, dmitrii.omelchenko@cloud.ionos.com
Subject: Re: [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes
Date: Mon, 17 Aug 2026 07:00:01 +0200	[thread overview]
Message-ID: <2026081730-denatured-spiral-61b2@gregkh> (raw)
In-Reply-To: <CAMGffEk4a8cF4utrMYpNvbcxBvuEhPnTY33_3GGs3RU4uy52vw@mail.gmail.com>

On Mon, Aug 17, 2026 at 06:51:27AM +0200, Jinpu Wang wrote:
> On Sat, Aug 15, 2026 at 4:33 AM Sasha Levin <sashal@kernel.org> wrote:
> >
> > > 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
> Hi Sasha,
> 
> Thanks for queueing the series.
> 
> It might be worth adding a rule for the stable-kernel scripts to
> ensure they don't pick a single patch from the middle of an upstream
> patchset. This could help prevent future regressions like this one,
> where a commit dropped functionality in anticipation of a counterpart
> commit that was left behind.

How do we "know" a patch is in the middle of a patchset just by looking
at the git tree?

thanks,

greg k-h

  reply	other threads:[~2026-08-17  5:01 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 ` [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes Sasha Levin
2026-08-17  4:51   ` Jinpu Wang
2026-08-17  5:00     ` Greg KH [this message]
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=2026081730-denatured-spiral-61b2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitrii.omelchenko@cloud.ionos.com \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=sashal@kernel.org \
    --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