linux-kernel - [PATCH] KVM: arm64:space prohibited between function name and open parenthesis '(';space required before the open parenthesis '('

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Thu, 13 Jul 2023 20:19:41 +0800
From:   chenqingyun001@...suo.com
To:     maz@...nel.org, oliver.upton@...ux.dev, catalin.marinas@....com,
        will@...nel.org
Cc:     kvmarm@...ts.linux.dev, linux-kernel@...r.kernel.org,
        james.morse@....com, suzuki.poulose@....com, yuzenghui@...wei.com
Subject: [PATCH] KVM: arm64:space prohibited between function name         and
 open parenthesis '(';space required       before the open parenthesis '('

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@...suo.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;