From: Oliver Upton <oliver.upton@linux.dev>
To: chenqingyun001@208suo.com
Cc: maz@kernel.org, catalin.marinas@arm.com, will@kernel.org,
kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org,
james.morse@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com
Subject: Re: [PATCH] KVM: arm64:Use #include <linux/cpufeature.h> instead of <asm/cpufeature.h> trailing whitespace braces {} are not necessary for any arm of this statement
Date: Wed, 12 Jul 2023 21:54:28 -0700 [thread overview]
Message-ID: <ZK+DhMfudVdhXnm2@thinky-boi> (raw)
In-Reply-To: <ef2ecfd960b2141b143003cc41ee551a@208suo.com>
Qingyun,
I'm guessing you did not read our developer documentation, nor did you
run scripts/checkpatch.pl...
- The shortlog should be at most 75 characters, but ideally less.
- The body should not be a restatement of the shortlog, and actually
provide meaningful information to the reader not yet captured in the
shortlog.
[*] https://www.kernel.org/doc/html/latest/process/submitting-patches.html
On Thu, Jul 13, 2023 at 11:03:44AM +0800, chenqingyun001@208suo.com wrote:
> include <linux/cpufeature.h> is a generic
> Having extra spaces or tabs has no real effect
> If there is only one statement in the if branch,
> curly braces {} can be omitted
>
> Signed-off-by: Qingyun Chen <chenqingyun001@208suo.com>
> ---
> arch/arm64/kvm/reset.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/kvm/reset.c b/arch/arm64/kvm/reset.c
> index b5dee8e57e77..4e6305dd1909 100644
> --- a/arch/arm64/kvm/reset.c
> +++ b/arch/arm64/kvm/reset.c
> @@ -19,7 +19,7 @@
>
> #include <kvm/arm_arch_timer.h>
>
> -#include <asm/cpufeature.h>
> +#include <linux/cpufeature.h>
Changing the include provides absolutely nothing of value. All the
things this compilation unit depends on are described in the asm header.
Furthermore, use of the asm header appears all throughout the arm64
code.
> #include <asm/cputype.h>
> #include <asm/fpsimd.h>
> #include <asm/ptrace.h>
> @@ -122,7 +122,7 @@ static int kvm_vcpu_finalize_sve(struct kvm_vcpu *vcpu)
> kfree(buf);
> return ret;
> }
> -
> +
> vcpu->arch.sve_state = buf;
> vcpu_set_flag(vcpu, VCPU_SVE_FINALIZED);
> return 0;
> @@ -308,9 +308,9 @@ int kvm_reset_vcpu(struct kvm_vcpu *vcpu)
>
> switch (vcpu->arch.target) {
> default:
> - if (vcpu_el1_is_32bit(vcpu)) {
> + if (vcpu_el1_is_32bit(vcpu))
> pstate = VCPU_RESET_PSTATE_SVC;
> - } else if (vcpu_has_nv(vcpu)) {
> + else if (vcpu_has_nv(vcpu)) {
No. What we have matches the kernel style guide. If one branch of a
conditional statement requires braces, _all_ branches get braces.
[*] https://www.kernel.org/doc/html/latest/process/coding-style.html#placing-braces-and-spaces
I strongly suggest you read up on the kernel developer documentation
before your next contribution, as you're unlikely to win any favors with
reviewers with problematic submissions such as this.
--
Thanks,
Oliver
prev parent reply other threads:[~2023-07-13 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_1B7BA6D8EFD533563E01F8EB64A145417008@qq.com>
2023-07-13 3:03 ` [PATCH] KVM: arm64:Use #include <linux/cpufeature.h> instead of <asm/cpufeature.h> trailing whitespace braces {} are not necessary for any arm of this statement chenqingyun001
2023-07-13 4:54 ` Oliver Upton [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=ZK+DhMfudVdhXnm2@thinky-boi \
--to=oliver.upton@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=chenqingyun001@208suo.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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