All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	jannh@google.com, ju.orth@gmail.com, shuah@kernel.org,
	stable@vger.kernel.org, torvalds@linux-foundation.org,
	vbabka@suse.cz
Subject: Re: FAILED: patch "[PATCH] mm: reinstate ability to map write-sealed memfd mappings" failed to apply to 6.6-stable tree
Date: Mon, 6 Jan 2025 13:10:01 +0100	[thread overview]
Message-ID: <2025010641-value-reassure-b741@gregkh> (raw)
In-Reply-To: <d583760e-38b7-484f-94a3-2c787107832f@lucifer.local>

On Mon, Jan 06, 2025 at 11:56:50AM +0000, Lorenzo Stoakes wrote:
> On Mon, Jan 06, 2025 at 11:19:17AM +0000, Lorenzo Stoakes wrote:
> > On Mon, Jan 06, 2025 at 12:06:52PM +0100, gregkh@linuxfoundation.org wrote:
> > >
> > > The patch below does not apply to the 6.6-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> >
> > I actually intentionally didn't add Cc: Stable there as I knew this needed
> > manual backport (to >=6.6.y... - the feature is only introduced in 6.6!) but I
> > guess it was added on.
> >
> > Now the auto-scripts fired anyway, can you confirm whether 6.12 got it or
> > not? To save me the effort of backporting this to 6.12 as well if I don't
> > need to.
> >
> > I'll send out a manual backport for 6.6.y shortly. Older stable kernels
> > obviously don't need this.
> 
> Correction - the feature I am fixing landed in 6.7, so no need for a backport to
> 6.6 then :)
> 
> Only 6.12 requires a backport.

Great, it applied cleanly there and is now queued up, thanks!

greg k-h

      reply	other threads:[~2025-01-06 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 11:06 FAILED: patch "[PATCH] mm: reinstate ability to map write-sealed memfd mappings" failed to apply to 6.6-stable tree gregkh
2025-01-06 11:19 ` Lorenzo Stoakes
2025-01-06 11:56   ` Lorenzo Stoakes
2025-01-06 12:10     ` 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=2025010641-value-reassure-b741@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=ju.orth@gmail.com \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.