From: Ian Rogers <irogers@google.com>
To: baomingtong001@208suo.com
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, namhyung@kernel.org, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf bench: remove unneeded variable
Date: Tue, 13 Jun 2023 21:43:32 -0700 [thread overview]
Message-ID: <CAP-5=fWtrQABXFnuAQWEuaFcvXJ5gaKf=gZUyTLqm8-aY9znrQ@mail.gmail.com> (raw)
In-Reply-To: <475df60d9dd518e20ae9df396c60b69b@208suo.com>
On Tue, Jun 13, 2023 at 8:38 PM <baomingtong001@208suo.com> wrote:
>
> fix the following coccicheck warning:
>
> tools/perf/bench/find-bit-bench.c:127:5-8: Unneeded variable: "err".
> Return "0".
>
> Signed-off-by: Mingtong Bao <baomingtong001@208suo.com>
Reviewed-by: Ian Rogers <irogers@google.com>
Thanks,
Ian
> ---
> tools/perf/bench/find-bit-bench.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/bench/find-bit-bench.c
> b/tools/perf/bench/find-bit-bench.c
> index 7e25b0e413f6..70619bc73841 100644
> --- a/tools/perf/bench/find-bit-bench.c
> +++ b/tools/perf/bench/find-bit-bench.c
> @@ -124,7 +124,7 @@ static int do_for_each_set_bit(unsigned int
> num_bits)
>
> int bench_mem_find_bit(int argc, const char **argv)
> {
> - int err = 0, i;
> + int i;
>
> argc = parse_options(argc, argv, options, bench_usage, 0);
> if (argc) {
> @@ -135,5 +135,5 @@ int bench_mem_find_bit(int argc, const char **argv)
> for (i = 1; i <= 2048; i <<= 1)
> do_for_each_set_bit(i);
>
> - return err;
> + return 0;
> }
next prev parent reply other threads:[~2023-06-14 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230614033437.48549-1-luojianhong@cdjrlc.com>
2023-06-14 3:38 ` [PATCH] perf bench: remove unneeded variable baomingtong001
2023-06-14 4:43 ` Ian Rogers [this message]
2023-06-14 13:59 ` Arnaldo Carvalho de Melo
2021-04-12 9:20 [PATCH] perf: bench: Remove " Wan Jiabing
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='CAP-5=fWtrQABXFnuAQWEuaFcvXJ5gaKf=gZUyTLqm8-aY9znrQ@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=baomingtong001@208suo.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 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).