From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: CGEL <cgel.zte@gmail.com>
Cc: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
linux-mips@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jing Yangyang <jing.yangyang@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] mips:mmu: fix boolreturn.cocci warnings
Date: Sun, 29 Aug 2021 13:36:22 +0200 [thread overview]
Message-ID: <20210829113622.GB4573@alpha.franken.de> (raw)
In-Reply-To: <20210824063004.59604-1-deng.changcheng@zte.com.cn>
On Mon, Aug 23, 2021 at 11:30:04PM -0700, CGEL wrote:
> From: Jing Yangyang <jing.yangyang@zte.com.cn>
>
> ./arch/mips/kvm/mmu.c:489:9-10:WARNING: return of 0/1 in function
> 'kvm_test_age_gfn' with return type bool
> ./arch/mips/kvm/mmu.c:445:8-9 WARNING: return of 0/1 in function
> 'kvm_unmap_gfn_range' with return type bool
>
> Return statements in functions returning bool should use true/false
> instead of 1/0.
>
> Generated by: scripts/coccinelle/misc/boolreturn.cocci
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Jing Yangyang <jing.yangyang@zte.com.cn>
> ---
> arch/mips/kvm/mmu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/kvm/mmu.c b/arch/mips/kvm/mmu.c
> index 6d1f68c..1bfd1b5 100644
> --- a/arch/mips/kvm/mmu.c
> +++ b/arch/mips/kvm/mmu.c
> @@ -442,7 +442,7 @@ static int kvm_mips_mkold_gpa_pt(struct kvm *kvm, gfn_t start_gfn,
> bool kvm_unmap_gfn_range(struct kvm *kvm, struct kvm_gfn_range *range)
> {
> kvm_mips_flush_gpa_pt(kvm, range->start, range->end);
> - return 1;
> + return true;
> }
>
> bool kvm_set_spte_gfn(struct kvm *kvm, struct kvm_gfn_range *range)
> @@ -486,7 +486,7 @@ bool kvm_test_age_gfn(struct kvm *kvm, struct kvm_gfn_range *range)
> pte_t *gpa_pte = kvm_mips_pte_for_gpa(kvm, NULL, gpa);
>
> if (!gpa_pte)
> - return 0;
> + return false;
> return pte_young(*gpa_pte);
this is already "fixed" in mips-next by
126b39368604 MIPS: Return true/false (not 1/0) from bool functions
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-08-29 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 6:30 CGEL
2021-08-29 11:36 ` Thomas Bogendoerfer [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=20210829113622.GB4573@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=cgel.zte@gmail.com \
--cc=jing.yangyang@zte.com.cn \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=zealci@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
all inboxes | Powered by JetHome®