From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: [PATCH 02/10] KVM: arm64: guest: fix kernel-doc warnings
Date: Wed, 17 Jan 2024 15:07:06 -0800 [thread overview]
Message-ID: <20240117230714.31025-3-rdunlap@infradead.org> (raw)
In-Reply-To: <20240117230714.31025-1-rdunlap@infradead.org>
Fix multiple function parameter descriptions to prevent warnings:
guest.c:718: warning: Function parameter or struct member 'vcpu' not described in 'kvm_arm_num_regs'
guest.c:736: warning: Function parameter or struct member 'vcpu' not described in 'kvm_arm_copy_reg_indices'
guest.c:736: warning: Function parameter or struct member 'uindices' not described in 'kvm_arm_copy_reg_indices'
arch/arm64/kvm/guest.c:915: warning: Excess function parameter 'kvm' description in 'kvm_arch_vcpu_ioctl_set_guest_debug'
arch/arm64/kvm/guest.c:915: warning: Excess function parameter 'kvm_guest_debug' description in 'kvm_arch_vcpu_ioctl_set_guest_debug'
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>
Cc: James Morse <james.morse@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Zenghui Yu <yuzenghui@huawei.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: kvmarm@lists.linux.dev
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>
---
arch/arm64/kvm/guest.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff -- a/arch/arm64/kvm/guest.c b/arch/arm64/kvm/guest.c
--- a/arch/arm64/kvm/guest.c
+++ b/arch/arm64/kvm/guest.c
@@ -711,6 +711,7 @@ static int copy_sve_reg_indices(const st
/**
* kvm_arm_num_regs - how many registers do we present via KVM_GET_ONE_REG
+ * @vcpu: the vCPU pointer
*
* This is for all registers.
*/
@@ -729,6 +730,8 @@ unsigned long kvm_arm_num_regs(struct kv
/**
* kvm_arm_copy_reg_indices - get indices of all registers.
+ * @vcpu: the vCPU pointer
+ * @uindices: register list to copy
*
* We do core registers right here, then we append system regs.
*/
@@ -902,8 +905,8 @@ int kvm_arch_vcpu_ioctl_translate(struct
/**
* kvm_arch_vcpu_ioctl_set_guest_debug - set up guest debugging
- * @kvm: pointer to the KVM struct
- * @kvm_guest_debug: the ioctl data buffer
+ * @vcpu: the vCPU pointer
+ * @dbg: the ioctl data buffer
*
* This sets up and enables the VM for guest debugging. Userspace
* passes in a control flag to enable different debug types and
next prev parent reply other threads:[~2024-01-17 23:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 23:07 [PATCH 00/10] KVM: arm64: fix many " Randy Dunlap
2024-01-17 23:07 ` [PATCH 01/10] KVM: arm64: debug: fix " Randy Dunlap
2024-01-17 23:07 ` Randy Dunlap [this message]
2024-01-17 23:07 ` [PATCH 03/10] KVM: arm64: hyp/aarch32: " Randy Dunlap
2024-01-17 23:07 ` [PATCH 04/10] KVM: arm64: vhe: fix a kernel-doc warning Randy Dunlap
2024-01-17 23:07 ` [PATCH 05/10] KVM: arm64: mmu: " Randy Dunlap
2024-01-17 23:07 ` [PATCH 06/10] KVM: arm64: PMU: fix kernel-doc warnings Randy Dunlap
2024-01-17 23:07 ` [PATCH 07/10] KVM: arm64: sys_regs: " Randy Dunlap
2024-01-17 23:07 ` [PATCH 08/10] KVM: arm64: vgic-init: fix a kernel-doc warning Randy Dunlap
2024-01-17 23:07 ` [PATCH 09/10] KVM: arm64: vgic-its: fix kernel-doc warnings Randy Dunlap
2024-01-17 23:07 ` [PATCH 10/10] KVM: arm64: vgic: fix a kernel-doc warning Randy Dunlap
2024-02-01 6:19 ` [PATCH 00/10] KVM: arm64: fix many kernel-doc warnings Randy Dunlap
2024-02-01 13:45 ` Marc Zyngier
2024-02-01 17:47 ` Oliver Upton
2024-02-01 10:23 ` Suzuki K Poulose
2024-02-01 13:49 ` Zenghui Yu
2024-02-01 20:30 ` Oliver Upton
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=20240117230714.31025-3-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--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®