From: Greg KH <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: roman.gushchin@linux.dev, akpm@linux-foundation.org,
seanjc@google.com, stable@vger.kernel.org, vbabka@suse.cz,
willy@infradead.org
Subject: Re: FAILED: patch "[PATCH] mm: page_alloc: move mlocked flag clearance into" failed to apply to 6.6-stable tree
Date: Tue, 10 Dec 2024 09:56:21 +0100 [thread overview]
Message-ID: <2024121011-cargo-crate-1828@gregkh> (raw)
In-Reply-To: <97594aca-8bfe-78d6-fa86-688af7610c83@google.com>
On Fri, Dec 06, 2024 at 02:21:38PM -0800, Hugh Dickins wrote:
> On Mon, 18 Nov 2024, Hugh Dickins wrote:
> > On Sun, 17 Nov 2024, 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>.
> > >
> > > To reproduce the conflict and resubmit, you may use the following commands:
> > >
> > > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.6.y
> > > git checkout FETCH_HEAD
> > > git cherry-pick -x 66edc3a5894c74f8887c8af23b97593a0dd0df4d
> > > # <resolve conflicts, build, test, etc.>
> > > git commit -s
> > > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2024111714-varsity-grub-d888@gregkh' --subject-prefix 'PATCH 6.6.y' HEAD^..
> >
> > For 6.6 and 6.1 please use this replacement patch:
>
> I notice that there's now a 6.6.64-rc1 out for review, but without
> Roman's mlocked flag clearance patch. No desperate need to get it into
> an rc of 6.6.64, but we wouldn't want it to go missing indefinitely.
Sorry for the delay, now queued up.
greg k-h
prev parent reply other threads:[~2024-12-10 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 20:29 FAILED: patch "[PATCH] mm: page_alloc: move mlocked flag clearance into" failed to apply to 6.6-stable tree gregkh
2024-11-18 19:28 ` Hugh Dickins
2024-11-19 4:36 ` Sasha Levin
2024-12-06 22:21 ` Hugh Dickins
2024-12-10 8:56 ` 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=2024121011-cargo-crate-1828@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=roman.gushchin@linux.dev \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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