KVM: arm64: Don't use kerneldoc comment for arm64_check_features()
authorOliver Upton <oliver.upton@linux.dev>
Wed, 13 Sep 2023 16:56:44 +0000 (16:56 +0000)
committerOliver Upton <oliver.upton@linux.dev>
Mon, 18 Sep 2023 17:08:21 +0000 (17:08 +0000)
A double-asterisk opening mark to the comment (i.e. '/**') indicates a
comment block is in the kerneldoc format. There's automation in place to
validate that kerneldoc blocks actually adhere to the formatting rules.

The function comment for arm64_check_features() isn't kerneldoc; use a
'regular' comment to silence automation warnings.

Link: https://lore.kernel.org/all/202309112251.e25LqfcK-lkp@intel.com/
Reviewed-by: Zenghui Yu <yuzenghui@huawei.com>
Link: https://lore.kernel.org/r/20230913165645.2319017-1-oliver.upton@linux.dev
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
arch/arm64/kvm/sys_regs.c

index e92ec810d4494bac8ec83c7f23d0a360d9651493..818a52e257eda376573cb6aa30601bd38c65fc9f 100644 (file)
@@ -1228,7 +1228,7 @@ static s64 kvm_arm64_ftr_safe_value(u32 id, const struct arm64_ftr_bits *ftrp,
        return arm64_ftr_safe_value(&kvm_ftr, new, cur);
 }
 
-/**
+/*
  * arm64_check_features() - Check if a feature register value constitutes
  * a subset of features indicated by the idreg's KVM sanitised limit.
  *