Linux Trace Kernel
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pekka Paalanen <ppaalanen@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, nouveau@lists.freedesktop.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] tracing/mmiotrace: Clean up coding style and redundant debug logs
Date: Sat, 8 Aug 2026 13:16:34 +0900	[thread overview]
Message-ID: <20260808131634.4dafadc203a58e9f5b0e7613@kernel.org> (raw)
In-Reply-To: <20260807205053.7000eef0@gandalf.local.home>

On Fri, 7 Aug 2026 20:50:53 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Tue, 28 Jul 2026 21:50:19 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> 
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> > Clean up coding style issues in trace_mmiotrace.c:
> > - Remove redundant pr_debug() entries in tracer callbacks.
> > - Fix opening brace placement for mmio_tracer.
> > - Prefer 'unsigned int' to bare 'unsigned'.
> > - Add missing blank lines after local variable declarations.
> > 
> > Assisted-by: Antigravity:gemini-3.6-flash
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > ---
> >  kernel/trace/trace_mmiotrace.c |   16 +++++++---------
> >  1 file changed, 7 insertions(+), 9 deletions(-)
> > 
> > diff --git a/kernel/trace/trace_mmiotrace.c b/kernel/trace/trace_mmiotrace.c
> > index 77120d467e11..ce16e1c53d12 100644
> > --- a/kernel/trace/trace_mmiotrace.c
> > +++ b/kernel/trace/trace_mmiotrace.c
> > @@ -36,7 +36,6 @@ static void mmio_reset_data(struct trace_array *tr)
> >  
> >  static int mmio_trace_init(struct trace_array *tr)
> >  {
> > -	pr_debug("in %s\n", __func__);
> 
> So how are these redundant?
> 
> Are there pr_debug() prints elsewhere?

No, that is not redundant, but just like only for debugging mmiotrace.
Maybe we can leave it.

[...]
> > @@ -322,6 +318,7 @@ static void __trace_mmiotrace_rw(struct trace_array *tr,
> >  void mmio_trace_rw(struct mmiotrace_rw *rw)
> >  {
> >  	struct trace_array *tr = mmio_trace_array;
> > +
> >  	__trace_mmiotrace_rw(tr, rw);
> >  }
> >  
> > @@ -353,6 +350,7 @@ static void __trace_mmiotrace_map(struct trace_array *tr,
> >  void mmio_trace_mapping(struct mmiotrace_map *map)
> >  {
> >  	struct trace_array *tr = mmio_trace_array;
> > +
> >  	__trace_mmiotrace_map(tr, map);
> >  }
> 
> Honestly, for one line functions like the above, I think it looks better
> without that blank line.
> 
> -- Steve

Yeah, this is somewhat machinary fix against the checkpatch.pl.
Or, maybe it is better to just pass mmio_trace_array directly?

Thanks,

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-08-08  4:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 12:49 [PATCH 0/4] tracing/mmiotrace: Fix some bugs in mmiotrace Masami Hiramatsu (Google)
2026-07-28 12:49 ` [PATCH 1/4] tracing/mmiotrace: Reset dropped_count in mmio_reset_data() Masami Hiramatsu (Google)
2026-07-28 12:50 ` [PATCH 2/4] tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions Masami Hiramatsu (Google)
2026-07-28 12:50 ` [PATCH 3/4] tracing/mmiotrace: Use trace_assign_type() in mmio_print_mark() Masami Hiramatsu (Google)
2026-07-28 12:50 ` [PATCH 4/4] tracing/mmiotrace: Clean up coding style and redundant debug logs Masami Hiramatsu (Google)
2026-08-08  0:50   ` Steven Rostedt
2026-08-08  4:16     ` Masami Hiramatsu [this message]
2026-08-08 13:12       ` 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=20260808131634.4dafadc203a58e9f5b0e7613@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=nouveau@lists.freedesktop.org \
    --cc=ppaalanen@gmail.com \
    --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