Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: bp@alien8.de, sashal@kernel.org, stable@kernel.org,
	stable@vger.kernel.org
Subject: Re: Patch "x86/sev: Guard sev_evict_cache() with CONFIG_AMD_MEM_ENCRYPT" has been added to the 6.12-stable tree
Date: Mon, 22 Sep 2025 16:08:29 +0200	[thread overview]
Message-ID: <2025092254-payment-rely-632c@gregkh> (raw)
In-Reply-To: <371ed3b2-8c7c-40bb-4e23-6a246a715168@amd.com>

On Mon, Sep 22, 2025 at 08:37:51AM -0500, Tom Lendacky wrote:
> On 9/22/25 00:52, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     x86/sev: Guard sev_evict_cache() with CONFIG_AMD_MEM_ENCRYPT
> > 
> > to the 6.12-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      x86-sev-guard-sev_evict_cache-with-config_amd_mem_encrypt.patch
> > and it can be found in the queue-6.12 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> Maybe I didn't use the tag correctly, but I put 6.16.x on the stable tag
> to indicate that the patch only applied to 6.16 and above. Before 6.16,
> there isn't a stub version of the function, so all off those releases
> are fine.
> 
> So this patch doesn't need to be part of the 6.12 stable tree.

Thanks for letting me know, I've now dropped this.  I was triggering off
of the "Fixes:" tag, which shows it was needed back to the 6.1.y tree.

thanks,

greg k-h

      reply	other threads:[~2025-09-22 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025092205-quaking-approve-4cd6@gregkh>
2025-09-22 13:37 ` Patch "x86/sev: Guard sev_evict_cache() with CONFIG_AMD_MEM_ENCRYPT" has been added to the 6.12-stable tree Tom Lendacky
2025-09-22 14:08   ` Greg KH [this message]

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=2025092254-payment-rely-632c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=sashal@kernel.org \
    --cc=stable@kernel.org \
    --cc=stable@vger.kernel.org \
    --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