From: Uladzislau Rezki <urezki@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: gregkh@linuxfoundation.org, urezki@gmail.com,
joelagnelf@nvidia.com, kbusch@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq" failed to apply to 6.12-stable tree
Date: Tue, 11 Mar 2025 17:13:29 +0100 [thread overview]
Message-ID: <Z9BhKRNXnI8uL57I@pc636> (raw)
In-Reply-To: <5ba8803f-4208-4f84-b24c-ea2cc8539849@suse.cz>
On Tue, Mar 11, 2025 at 05:11:44PM +0100, Vlastimil Babka wrote:
> On 3/9/25 7:16 PM, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.12-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>.
>
> Must be the code move from rcu to slab. Ulad, will you handle this, or
> should I? Thanks.
>
I will handle this.
--
Uladzislau Rezki
prev parent reply other threads:[~2025-03-11 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 18:16 FAILED: patch "[PATCH] mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq" failed to apply to 6.12-stable tree gregkh
2025-03-11 16:11 ` Vlastimil Babka
2025-03-11 16:13 ` Uladzislau Rezki [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=Z9BhKRNXnI8uL57I@pc636 \
--to=urezki@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joelagnelf@nvidia.com \
--cc=kbusch@kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox