linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: Benjamin Peterson <benjamin@engflow.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf trace: Remove return value of trace__fprintf_tp_fields
Date: Wed, 22 Jan 2025 11:08:08 -0800	[thread overview]
Message-ID: <Z5FCGGBxBHD95zjT@google.com> (raw)
In-Reply-To: <CAH0uvohQvqRYo8JBX_Z1yVobqcxRgQG4G1Y8o8XMv18CnrqBbA@mail.gmail.com>

Hello,

On Tue, Jan 21, 2025 at 07:01:53PM -0800, Howard Chu wrote:
> Hello fellow maintainers,
> 
> Just a slight ping.

Thanks for the reminder.

> 
> Thanks,
> Howard
> 
> On Fri, Dec 13, 2024 at 10:06 AM Howard Chu <howardchu95@gmail.com> wrote:
> >
> > Hello Benjamin,
> >
> > On Thu, Dec 12, 2024 at 7:56 PM Benjamin Peterson <benjamin@engflow.com> wrote:
> > >
> > > The return value of this function was meaningless and therefore ignored by
> > > the caller. Remove it.

In fact, I don't see the reason to merge this, as it's the convention to
return the number of characters it prints.  Yes, it's not used but not
much reason to remove it.

Thanks,
Namhyung

> > >
> > > Signed-off-by: Benjamin Peterson <benjamin@engflow.com>
> > > ---
> > > This is a small followup cleanup to my earlier commit 5fb8e56542a3 ("perf
> > > trace: avoid garbage when not printing a trace event's arguments").
> > > ---
> > >  tools/perf/builtin-trace.c | 6 +++---
> > >  1 file changed, 3 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> > > index 6a1a128fe645014d0347ad4ec3e0c9e77ec59aee..246be66fd59a4b9d76e4d3c42b68d0a444ca366a 100644
> > > --- a/tools/perf/builtin-trace.c
> > > +++ b/tools/perf/builtin-trace.c
> > > @@ -3022,8 +3022,8 @@ static void bpf_output__fprintf(struct trace *trace,
> > >         ++trace->nr_events_printed;
> > >  }
> > >
> > > -static size_t trace__fprintf_tp_fields(struct trace *trace, struct evsel *evsel, struct perf_sample *sample,
> > > -                                      struct thread *thread, void *augmented_args, int augmented_args_size)
> > > +static void trace__fprintf_tp_fields(struct trace *trace, struct evsel *evsel, struct perf_sample *sample,
> > > +                                    struct thread *thread, void *augmented_args, int augmented_args_size)
> > >  {
> > >         char bf[2048];
> > >         size_t size = sizeof(bf);
> > > @@ -3088,7 +3088,7 @@ static size_t trace__fprintf_tp_fields(struct trace *trace, struct evsel *evsel,
> > >                 printed += syscall_arg_fmt__scnprintf_val(arg, bf + printed, size - printed, &syscall_arg, val);
> > >         }
> > >
> > > -       return printed + fprintf(trace->output, "%.*s", (int)printed, bf);
> > > +       fprintf(trace->output, "%.*s", (int)printed, bf);
> > >  }
> > >
> > >  static int trace__event_handler(struct trace *trace, struct evsel *evsel,
> > >
> > > ---
> > > base-commit: eefa7a9c069908412f8f5d15833901d1b46ae1b2
> > > change-id: 20241212-void-fprintf_tp_fields-8aaae2f5525f
> > >
> > > Best regards,
> > > --
> > > Benjamin Peterson <benjamin@engflow.com>
> > >
> > >
> >
> > Thank you for the follow-up patch, LGTM. Built and tested.
> >
> > perf $ ./perf test "perf trace"
> > 109: perf trace enum augmentation tests                              : Ok
> > 110: perf trace exit race                                            : Ok
> >
> > Reviewed-by: Howard Chu <howardchu95@gmail.com>
> >
> > Thanks,
> > Howard

  reply	other threads:[~2025-01-22 19:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  3:56 [PATCH] perf trace: Remove return value of trace__fprintf_tp_fields Benjamin Peterson
2024-12-13 18:06 ` Howard Chu
2025-01-22  3:01   ` Howard Chu
2025-01-22 19:08     ` Namhyung Kim [this message]
2025-01-22 19:19       ` Benjamin Peterson
2025-01-23 23:48         ` Namhyung Kim
2025-01-24 17:37           ` Benjamin Peterson

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=Z5FCGGBxBHD95zjT@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=benjamin@engflow.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).