From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] tracing: Some cleanups of event trigger code
Date: Mon, 12 May 2025 15:47:53 -0500 [thread overview]
Message-ID: <cd64a829c2c76279ccce2640d55b97ecdb6368a3.camel@kernel.org> (raw)
In-Reply-To: <20250507145305.730136036@goodmis.org>
Hi Steve,
On Wed, 2025-05-07 at 10:53 -0400, Steven Rostedt wrote:
> These are minor clean ups of the trace_events_trigger code.
>
> - Rename event_trigger_alloc() to trigger_data_alloc() as it
> is supposed to be freed by trigger_data_free().
>
> - Remove unneeded goto outs
>
> - Add consistent cleanup in event_trigger_parse()
>
>
> Miaoqian Lin (1):
> tracing: Fix error handling in event_trigger_parse()
>
> Steven Rostedt (2):
> tracing: Rename event_trigger_alloc() to trigger_data_alloc()
> tracing: Remove unnecessary "goto out" that simply returns ret
> is trigger code
>
These all look right to me, and were probably the original intent.
For all 3,
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
Thanks,
Tom
> ----
> kernel/trace/trace.h | 8 ++---
> kernel/trace/trace_events_hist.c | 2 +-
> kernel/trace/trace_events_trigger.c | 64 ++++++++++++++++-----------
> ----------
> 3 files changed, 31 insertions(+), 43 deletions(-)
next prev parent reply other threads:[~2025-05-12 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 14:53 [PATCH 0/3] tracing: Some cleanups of event trigger code Steven Rostedt
2025-05-07 14:53 ` [PATCH 1/3] tracing: Rename event_trigger_alloc() to trigger_data_alloc() Steven Rostedt
2025-05-07 14:53 ` [PATCH 2/3] tracing: Fix error handling in event_trigger_parse() Steven Rostedt
2025-05-07 14:53 ` [PATCH 3/3] tracing: Remove unnecessary "goto out" that simply returns ret is trigger code Steven Rostedt
2025-05-12 20:47 ` Tom Zanussi [this message]
2025-05-12 20:50 ` [PATCH 0/3] tracing: Some cleanups of event " 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=cd64a829c2c76279ccce2640d55b97ecdb6368a3.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=akpm@linux-foundation.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