From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Joel Fernandes <joel@joelfernandes.org>,
Tom Zanussi <zanussi@kernel.org>
Subject: Re: [PATCH] tracing: Add trace_trigger kernel command line option
Date: Thu, 20 Oct 2022 18:23:47 -0400 [thread overview]
Message-ID: <20221020182347.3c09f718@gandalf.local.home> (raw)
In-Reply-To: <20221020222108.GZ5600@paulmck-ThinkPad-P17-Gen-1>
On Thu, 20 Oct 2022 15:21:08 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> My plan is to push it in after a bit of testing. The Fixes tag should
> make the right -stable stuff happen.
Great, thanks!
I'll resend my patch without the synchronize_rcu() avoidance.
-- Steve
next prev parent reply other threads:[~2022-10-20 22:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 0:01 [PATCH] tracing: Add trace_trigger kernel command line option Steven Rostedt
2022-10-20 0:07 ` Steven Rostedt
2022-10-20 15:59 ` Paul E. McKenney
2022-10-20 16:33 ` Steven Rostedt
2022-10-20 16:44 ` Joel Fernandes
2022-10-20 17:05 ` Steven Rostedt
2022-10-20 17:55 ` Paul E. McKenney
2022-10-20 18:53 ` Steven Rostedt
2022-10-20 22:21 ` Paul E. McKenney
2022-10-20 22:23 ` Steven Rostedt [this message]
2022-10-20 17:54 ` Paul E. McKenney
2022-10-20 7:49 ` kernel test robot
2022-10-20 8:50 ` kernel test robot
2022-10-20 14:33 ` Masami Hiramatsu
2022-10-20 15:20 ` Steven Rostedt
2022-10-20 14:43 ` Joel Fernandes
2022-10-20 14:52 ` Joel Fernandes
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=20221020182347.3c09f718@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=zanussi@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