From: Ingo Molnar <mingo@kernel.org>
To: Wen Yang <wen.yang99@zte.com.cn>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-kernel@vger.kernel.org, zhong.weidong@zte.com.cn,
"Peter Zijlstra (Intel)" <peterz@infraded.org>,
Peter Zijlstra <peterz@infradead.org>,
Mukesh Ojha <mojha@codeaurora.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] cpu: Bool tests don't need comparisons
Date: Mon, 3 Dec 2018 10:15:22 +0100 [thread overview]
Message-ID: <20181203091522.GC2516@gmail.com> (raw)
In-Reply-To: <20181201080444.9305-1-wen.yang99@zte.com.cn>
* Wen Yang <wen.yang99@zte.com.cn> wrote:
> This is the patch to the file cpu.c
> which fixes the following coccinelle warning:
>
> WARNING: Comparison to bool
>
> Signed-off-by: Wen Yang <wen.yang99@zte.com.cn>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: Ingo Molnar <mingo@kernel.org>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> CC: Josh Poimboeuf <jpoimboe@redhat.com>
> CC: "Peter Zijlstra (Intel)" <peterz@infraded.org>
> CC: Peter Zijlstra <peterz@infradead.org>
> CC: Mukesh Ojha <mojha@codeaurora.org>
> CC: linux-kernel@vger.kernel.org
> ---
> kernel/cpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index 91d5c38eb7e5..5bdd7e150a11 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -1650,7 +1650,7 @@ int __cpuhp_state_add_instance_cpuslocked(enum cpuhp_state state,
> lockdep_assert_cpus_held();
>
> sp = cpuhp_get_step(state);
> - if (sp->multi_instance == false)
> + if (!sp->multi_instance)
> return -EINVAL;
>
This is a *totally* bogus explanation.
This is an equivalent pattern to '== 0' which is commonly used.
The patch is still doing the right thing, but only accidentally, for
another reason, it's because we are using ->multi_instance in an
inconsistent fashion:
kernel/cpu.c: if (!step->multi_instance) {
kernel/cpu.c: if (sp->multi_instance == false)
kernel/cpu.c: if (!sp->multi_instance)
kernel/cpu.c: if (sp->multi_instance) {
But that's really just by accident - if all usages were of the
'== true/false' pattern then this wouldn't be necessary.
Thanks,
Ingo
prev parent reply other threads:[~2018-12-03 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 8:04 [PATCH] cpu: Bool tests don't need comparisons Wen Yang
2018-12-03 9:15 ` Ingo Molnar [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=20181203091522.GC2516@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=jpoimboe@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mojha@codeaurora.org \
--cc=peterz@infradead.org \
--cc=peterz@infraded.org \
--cc=tglx@linutronix.de \
--cc=wen.yang99@zte.com.cn \
--cc=zhong.weidong@zte.com.cn \
/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