From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
rcu@vger.kernel.org, kernel-dev@igalia.com, kernel@gpiccoli.net,
"Paul E . McKenney" <paulmck@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels
Date: Tue, 13 Dec 2022 20:41:58 -0300 [thread overview]
Message-ID: <49ccbce5-d2f9-c09f-b0b0-c4ba467f4a0c@igalia.com> (raw)
In-Reply-To: <20221213173425.609618fb@gandalf.local.home>
On 13/12/2022 19:34, Steven Rostedt wrote:
> On Tue, 13 Dec 2022 19:04:41 -0300
> "Guilherme G. Piccoli" <gpiccoli@igalia.com> wrote:
>
>> Hi Steve, sorry to annoy, just a regular ping to see if we can get this
>> into 6.2 (if too late, not a huge deal).
>
> Thanks for the ping. For some reason this patch didn't make it into my
> internal Patchwork, so I missed it (even though I did reply to you, I just
> assumed it was in my patchwork).
>
> It's not too late. I have some last minute patches I'm still testing. I'll
> queue this one up.
>
> BTW, we now have a kernel ftrace mailing list that you can Cc (but still Cc
> LKML).
>
> linux-trace-kernel@vger.kernel.org
>
> -- Steve
Tnx a lot Steve! I'll start to CC this list as well.
Cheers,
Guilherme
prev parent reply other threads:[~2022-12-13 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 20:48 Guilherme G. Piccoli
2022-11-16 6:36 ` Masami Hiramatsu
2022-11-16 12:45 ` Guilherme G. Piccoli
2022-11-22 13:16 ` Guilherme G. Piccoli
2022-11-22 15:49 ` Steven Rostedt
2022-11-22 17:21 ` Guilherme G. Piccoli
2022-12-13 22:04 ` Guilherme G. Piccoli
2022-12-13 22:34 ` Steven Rostedt
2022-12-13 23:41 ` Guilherme G. Piccoli [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=49ccbce5-d2f9-c09f-b0b0-c4ba467f4a0c@igalia.com \
--to=gpiccoli@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®