public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH v2] tracing: Remove definition of trace_*_rcuidle()
Date: Fri, 4 Oct 2024 11:59:07 +0200	[thread overview]
Message-ID: <20241004095907.GL18071@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241003181629.36209057@gandalf.local.home>

On Thu, Oct 03, 2024 at 06:16:29PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
> 
> The trace_*_rcuidle() variant of a tracepoint was to handle places where a
> tracepoint was located but RCU was not "watching". All those locations
> have been removed, and RCU should be watching where all tracepoints are
> located. We can now remove the trace_*_rcuidle() variant.
> 
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---

W00t

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

  reply	other threads:[~2024-10-04  9:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 22:16 [PATCH v2] tracing: Remove definition of trace_*_rcuidle() Steven Rostedt
2024-10-04  9:59 ` Peter Zijlstra [this message]
2024-12-03 19:33 ` Geert Uytterhoeven
2024-12-03 20:39 ` Guenter Roeck
2024-12-03 20:55   ` Steven Rostedt
2024-12-04  1:48     ` Guenter Roeck
2024-12-04  3:01       ` Steven Rostedt
2024-12-04  5:01         ` Paul E. McKenney
2024-12-04 14:33           ` Steven Rostedt
2024-12-04 15:47             ` Paul E. McKenney
2024-12-04  5:16         ` Guenter Roeck
2024-12-04  7:50         ` Geert Uytterhoeven
2024-12-05  9:31         ` Madhavan Srinivasan
2024-12-05 17:32 ` 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=20241004095907.GL18071@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@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