From: Marc Zyngier <maz@kernel.org>
To: kernel test robot <lkp@intel.com>,
Sean Christopherson <seanjc@google.com>
Cc: Danmei Wei <danmei.wei@intel.com>, Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Farrah Chen <farrah.chen@intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kbuild-all@lists.01.org,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Robert Hu <robert.hu@intel.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
James Morse <james.morse@arm.com>
Subject: Re: [PATCH] KVM: arm64: fix boolreturn.cocci warnings
Date: Tue, 11 May 2021 18:07:38 +0100 [thread overview]
Message-ID: <162075284668.2048815.12157825442810113360.b4-ty@kernel.org> (raw)
In-Reply-To: <20210426223357.GA45871@cd4295a34ed8>
On Tue, 27 Apr 2021 06:33:57 +0800, kernel test robot wrote:
> arch/arm64/kvm/mmu.c:1114:9-10: WARNING: return of 0/1 in function 'kvm_age_gfn' with return type bool
> arch/arm64/kvm/mmu.c:1084:9-10: WARNING: return of 0/1 in function 'kvm_set_spte_gfn' with return type bool
> arch/arm64/kvm/mmu.c:1127:9-10: WARNING: return of 0/1 in function 'kvm_test_age_gfn' with return type bool
> arch/arm64/kvm/mmu.c:1070:9-10: 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
Applied to fixes, thanks!
[1/1] KVM: arm64: fix boolreturn.cocci warnings
commit: 9ff40461a0e9684d8cb60058938004ddc16fb536
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-05-11 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 22:33 [kvm:queue 134/252] arch/arm64/kvm/mmu.c:1114:9-10: WARNING: return of 0/1 in function 'kvm_age_gfn' with return type bool kernel test robot
2021-04-26 22:33 ` [PATCH] KVM: arm64: fix boolreturn.cocci warnings kernel test robot
2021-05-11 16:29 ` Sean Christopherson
2021-05-11 17:07 ` Marc Zyngier [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=162075284668.2048815.12157825442810113360.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=danmei.wei@intel.com \
--cc=farrah.chen@intel.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=pbonzini@redhat.com \
--cc=robert.hu@intel.com \
--cc=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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).