From: Steven Rostedt <rostedt@goodmis.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Julia Lawall <Julia.Lawall@inria.fr>,
kernel-janitors@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
Date: Tue, 11 Jun 2024 10:14:58 -0400 [thread overview]
Message-ID: <20240611101458.7fa78da8@gandalf.local.home> (raw)
In-Reply-To: <05ec743a-c4e9-4c66-b2cd-4e89c858d7d4@suse.cz>
On Tue, 11 Jun 2024 10:42:28 +0200
Vlastimil Babka <vbabka@suse.cz> wrote:
> AFAICS that documented way is for a different situation? I assume you mean
> this part:
>
> * Specify any additional patch prerequisites for cherry picking::
>
> Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
>
> But that would assume we actively want to backport this cleanup patch in the
> first place. But as I understand Steven's intention, we want just to make
> sure that if in the future this patch is backported (i.e. as a dependency of
> something else) it won't be forgotten to also backport c9929f0e344a
> ("mm/slob: remove CONFIG_SLOB"). How to express that without actively
> marking this patch for backport at the same time?
Exactly! This isn't to be tagged as stable. It's just a way to say "if you
need this patch for any reason, you also need patch X".
I think "Depends-on" is the way to go, as it is *not* a stable thing, and
what is in stable rules is only about stable patches.
-- Steve
next prev parent reply other threads:[~2024-06-11 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240609082726.32742-1-Julia.Lawall@inria.fr>
[not found] ` <20240609082726.32742-6-Julia.Lawall@inria.fr>
[not found] ` <20240610112223.151faf65@rorschach.local.home>
[not found] ` <b647eacd-f6f3-4960-acfd-36c30f376995@paulmck-laptop>
[not found] ` <20240610163606.069d552a@gandalf.local.home>
2024-06-10 21:40 ` Vlastimil Babka
2024-06-11 6:23 ` Greg KH
2024-06-11 8:42 ` Vlastimil Babka
2024-06-11 9:05 ` Thorsten Leemhuis
2024-06-11 14:14 ` Steven Rostedt [this message]
2024-06-12 14:09 ` Jason A. Donenfeld
2024-06-12 16:04 ` Steven Rostedt
2024-06-11 14:12 ` Steven Rostedt
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=20240611101458.7fa78da8@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Julia.Lawall@inria.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=vbabka@suse.cz \
--cc=workflows@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