From: Leon Hwang <leon.hwang@linux.dev>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jiri Olsa <jolsa@kernel.org>, Andrii Nakryiko <andrii@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Leon Hwang <leon.hwang@linux.dev>
Subject: [PATCH 4/4] ftrace: Drop extra comma in trace_buffered_event_enable
Date: Thu, 30 Jul 2026 23:04:11 +0800 [thread overview]
Message-ID: <20260730150411.88667-5-leon.hwang@linux.dev> (raw)
In-Reply-To: <20260730150411.88667-1-leon.hwang@linux.dev>
Drop the extra comma in "scoped_guard()" to cleanup the code.
Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
---
kernel/trace/trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 19cc07360005..19b0d7a53c58 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1788,7 +1788,7 @@ void trace_buffered_event_enable(void)
per_cpu(trace_buffered_event, cpu) = event;
- scoped_guard(preempt,) {
+ scoped_guard(preempt) {
if (cpu == smp_processor_id() &&
__this_cpu_read(trace_buffered_event) !=
per_cpu(trace_buffered_event, cpu))
--
2.55.0
prev parent reply other threads:[~2026-07-30 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 15:04 [PATCH 0/4] ftrace: Protect RCU accesses to direct_functions Leon Hwang
2026-07-30 15:04 ` [PATCH 1/4] ftrace: Protect direct_functions in ftrace_find_rec_direct Leon Hwang
2026-07-30 15:04 ` [PATCH 2/4] ftrace: Protect direct_functions in update_ftrace_direct_del Leon Hwang
2026-07-30 15:04 ` [PATCH 3/4] ftrace: Protect direct_functions in update_ftrace_direct_mod Leon Hwang
2026-07-30 15:04 ` Leon Hwang [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=20260730150411.88667-5-leon.hwang@linux.dev \
--to=leon.hwang@linux.dev \
--cc=andrii@kernel.org \
--cc=jolsa@kernel.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