From: Namhyung Kim <namhyung@kernel.org>
To: Benjamin Peterson <benjamin@engflow.com>
Cc: Howard Chu <howardchu95@gmail.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: Thu, 23 Jan 2025 15:48:50 -0800 [thread overview]
Message-ID: <Z5LVYtjPZduzcoE-@google.com> (raw)
In-Reply-To: <CAEmfU+tj6kUbRNe7YbCorRStyAKs=7ndj73BvPUpkwA-gcBZCg@mail.gmail.com>
On Wed, Jan 22, 2025 at 11:19:05AM -0800, Benjamin Peterson wrote:
> On Wed, Jan 22, 2025 at 11:08 AM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > 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 for taking a look.
>
> >
> > >
> > > 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.
>
> The main reason to remove the return value is that it has no useful
> interpretation and is therefore confusing. To wit, the function
> returns two times the number of bytes it prints.
Oh, ok. Then please just fix it to return the correct number.
Thanks,
Namhyung
next prev parent reply other threads:[~2025-01-23 23:48 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
2025-01-22 19:19 ` Benjamin Peterson
2025-01-23 23:48 ` Namhyung Kim [this message]
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=Z5LVYtjPZduzcoE-@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.