From: chenqingyun001@208suo.com
To: maz@kernel.org, oliver.upton@linux.dev, catalin.marinas@arm.com,
will@kernel.org
Cc: kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org,
james.morse@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com
Subject: [PATCH] KVM: arm64:space prohibited between function name and open parenthesis '(';space required before the open parenthesis '('
Date: Thu, 13 Jul 2023 20:19:41 +0800 [thread overview]
Message-ID: <a9d6a2ccfa775c0ea91032ac5c76ea8e@208suo.com> (raw)
In-Reply-To: <tencent_A24E3EC2F8CE6474455D704AA667EF103308@qq.com>
Using spaces can affect the readability and consistency
of your code. If you use a space between the function name
and the opening parenthesis, it may be mistaken for the
function name instead of the actual function name.
Use spaces between keywords and opening parentheses to
distinguish function calls from control statements
Signed-off-by: Qingyun Chen <chenqingyun001@208suo.com>
---
arch/arm64/kvm/hyp/exception.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kvm/hyp/exception.c
b/arch/arm64/kvm/hyp/exception.c
index 424a5107cddb..46888dba3def 100644
--- a/arch/arm64/kvm/hyp/exception.c
+++ b/arch/arm64/kvm/hyp/exception.c
@@ -16,7 +16,7 @@
#include <asm/kvm_mmu.h>
#include <asm/kvm_nested.h>
-#if !defined (__KVM_NVHE_HYPERVISOR__) && !defined
(__KVM_VHE_HYPERVISOR__)
+#if !defined(__KVM_NVHE_HYPERVISOR__) &&
!defined(__KVM_VHE_HYPERVISOR__)
#error Hypervisor code only!
#endif
@@ -295,7 +295,7 @@ static void enter_exception32(struct kvm_vcpu *vcpu,
u32 mode, u32 vect_offset)
return_address += return_offsets[vect_offset >> 2][is_thumb];
/* KVM only enters the ABT and UND modes, so only deal with those
*/
- switch(mode) {
+ switch (mode) {
case PSR_AA32_MODE_ABT:
__vcpu_write_spsr_abt(vcpu, host_spsr_to_spsr32(spsr));
vcpu_gp_regs(vcpu)->compat_lr_abt = return_address;
parent reply other threads:[~2023-07-13 12:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_A24E3EC2F8CE6474455D704AA667EF103308@qq.com>]
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=a9d6a2ccfa775c0ea91032ac5c76ea8e@208suo.com \
--to=chenqingyun001@208suo.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--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
all inboxes | Powered by JetHome®