From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
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>,
Peter Zijlstra <peterz@infradead.org>,
Joel Fernandes <joel@joelfernandes.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Paul Burton <paulburton@kernel.org>
Subject: Re: [PATCH v2] tracing: Remove definition of trace_*_rcuidle()
Date: Wed, 4 Dec 2024 09:33:56 -0500 [thread overview]
Message-ID: <20241204093356.2d578657@gandalf.local.home> (raw)
In-Reply-To: <60749a43-17ad-4491-a13f-a2db7b6cb00c@paulmck-laptop>
On Tue, 3 Dec 2024 21:01:59 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> > Paul?
>
> Looks plausible to me, though I don't understand why the introduction
> of trace() doesn't permit removal of the corresponding current code.
> (Or did I miss a previous patch that did just that?)
>
I removed the trace_*_rcuidle() code, but this file still used it. I didn't
realize that removing the trace_*_rcuidle() in this file would break other
architectures.
This patch is a work around to not need to re-introduce the
trace_*_rcuidle() code.
-- Steve
next prev parent reply other threads:[~2024-12-04 14:33 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
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 [this message]
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=20241204093356.2d578657@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulburton@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tsbogend@alpha.franken.de \
/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