From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: baomingtong001@208suo.com, peterz@infradead.org,
mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, adrian.hunter@intel.com,
anshuman.khandual@arm.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools:remove unneeded variable from perf_event_attr__fprintf()
Date: Wed, 3 Jan 2024 18:19:49 -0300 [thread overview]
Message-ID: <ZZXPdSo38DRTUVj_@kernel.org> (raw)
In-Reply-To: <CAP-5=fW_tgXjWpevy+y4gY5XxpYq27zHahPZ8fv5L3+LdjaFnQ@mail.gmail.com>
Em Wed, Jul 12, 2023 at 06:20:12PM -0700, Ian Rogers escreveu:
> On Tue, Jun 13, 2023 at 11:25 PM <baomingtong001@208suo.com> wrote:
> >
> > fix the following coccicheck warning:
> >
> > tools/perf/util/perf_event_attr_fprintf.c:97:5-8: Unneeded variable:
> > "ret". Return "0".
> >
> > Signed-off-by: Mingtong Bao <baomingtong001@208suo.com>
>
> Acked-by: Ian Rogers <irogers@google.com>
util/perf_event_attr_fprintf.c: In function ‘perf_event_attr__fprintf’:
util/perf_event_attr_fprintf.c:256:17: error: ‘ret’ undeclared (first use in this function)
256 | ret += attr__fprintf(fp, _n, buf, priv);\
| ^~~
util/perf_event_attr_fprintf.c:267:9: note: in expansion of macro ‘PRINT_ATTRn’
267 | PRINT_ATTRn("type", type, p_type_id, true);
| ^~~~~~~~~~~
All those PRINT_ATTRf use that ret variable:
#define PRINT_ATTRn(_n, _f, _p, _a) \
do { \
if (_a || attr->_f) { \
_p(attr->_f); \
ret += attr__fprintf(fp, _n, buf, priv);\
} \
} while (0)
#define PRINT_ATTRf(_f, _p) PRINT_ATTRn(#_f, _f, _p, false
- Arnaldo
> Thanks,
> Ian
>
> > ---
> > tools/perf/util/perf_event_attr_fprintf.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/tools/perf/util/perf_event_attr_fprintf.c
> > b/tools/perf/util/perf_event_attr_fprintf.c
> > index 7e5e7b30510d..4a8f625b80c7 100644
> > --- a/tools/perf/util/perf_event_attr_fprintf.c
> > +++ b/tools/perf/util/perf_event_attr_fprintf.c
> > @@ -94,7 +94,6 @@ int perf_event_attr__fprintf(FILE *fp, struct
> > perf_event_attr *attr,
> > attr__fprintf_f attr__fprintf, void *priv)
> > {
> > char buf[BUF_SIZE];
> > - int ret = 0;
> >
> > PRINT_ATTRf(type, p_unsigned);
> > PRINT_ATTRf(size, p_unsigned);
> > @@ -155,5 +154,5 @@ int perf_event_attr__fprintf(FILE *fp, struct
> > perf_event_attr *attr,
> > PRINT_ATTRf(aux_sample_size, p_unsigned);
> > PRINT_ATTRf(sig_data, p_unsigned);
> >
> > - return ret;
> > + return 0;
> > }
--
- Arnaldo
prev parent reply other threads:[~2024-01-03 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230614062234.24149-1-luojianhong@cdjrlc.com>
2023-06-14 6:25 ` [PATCH] perf tools:remove unneeded variable from perf_event_attr__fprintf() baomingtong001
2023-07-13 1:20 ` Ian Rogers
2024-01-03 21:19 ` Arnaldo Carvalho de Melo [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=ZZXPdSo38DRTUVj_@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=baomingtong001@208suo.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=namhyung@kernel.org \
--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.