From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Haoyang LIU <tttturtleruss@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org (open list:TRACING),
linux-trace-kernel@vger.kernel.org (open list:TRACING)
Subject: Re: [PATCH] tracing: Fix indentation of return statement in print_trace_fmt()
Date: Thu, 29 Jan 2026 11:29:05 +0900 [thread overview]
Message-ID: <20260129112905.5840a45972274dd0048e36f3@kernel.org> (raw)
In-Reply-To: <20260129013954.5325-1-tttturtleruss@gmail.com>
On Thu, 29 Jan 2026 09:39:54 +0800
Haoyang LIU <tttturtleruss@gmail.com> wrote:
> The return statement inside the nested if block in print_trace_fmt()
> is not properly indented, making the code structure unclear. This was
> flagged by smatch as a warning.
>
> Add proper indentation to the return statement to match the kernel
> coding style and improve readability.
>
> Signed-off-by: Haoyang LIU <tttturtleruss@gmail.com>
Looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thanks,
> ---
> 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 8bd4ec08fb36..bf0ce2aac177 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -4286,7 +4286,7 @@ static enum print_line_t print_trace_fmt(struct trace_iterator *iter)
> /* ftrace and system call events are still OK */
> if ((event->type > __TRACE_LAST_TYPE) &&
> !is_syscall_event(event))
> - return print_event_fields(iter, event);
> + return print_event_fields(iter, event);
> }
> return event->funcs->trace(iter, sym_flags, event);
> }
> --
> 2.25.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-01-29 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 1:39 [PATCH] tracing: Fix indentation of return statement in print_trace_fmt() Haoyang LIU
2026-01-29 2:29 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-10 15:39 Haoyang LIU
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=20260129112905.5840a45972274dd0048e36f3@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=tttturtleruss@gmail.com \
/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