From: Randy Dunlap <rdunlap@infradead.org>
To: "Li, Fei1" <fei1.li@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "acrn-dev@lists.projectacrn.org" <acrn-dev@lists.projectacrn.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] virt: acrn: fix kernel-doc in <uapi/linux/acrn.h>
Date: Thu, 23 Oct 2025 23:06:00 -0700 [thread overview]
Message-ID: <213c918b-b4aa-4174-af89-a4d17e8c30dc@infradead.org> (raw)
In-Reply-To: <SJ1PR11MB615389E066F50BBB68686A26BFF1A@SJ1PR11MB6153.namprd11.prod.outlook.com>
Hi,
On 10/23/25 11:00 PM, Li, Fei1 wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>> Sent: Friday, October 24, 2025 12:42 PM
>> To: linux-kernel@vger.kernel.org
>> Cc: Randy Dunlap <rdunlap@infradead.org>; Li, Fei1 <fei1.li@intel.com>;
>> acrn-dev@lists.projectacrn.org; Greg Kroah-Hartman
>> <gregkh@linuxfoundation.org>
>> Subject: [PATCH] virt: acrn: fix kernel-doc in <uapi/linux/acrn.h>
>>
>> Fix the kernel-doc comments for struct acrn_mmiodev so that all struct
>> members are rendered correctly.
>> Correct io_base to io_addr in struct acrn_vdev.
>>
>> acrn.h:441: warning: Function parameter or struct member 'res'
>> not described in 'acrn_mmiodev'
>> acrn.h:479: warning: Function parameter or struct member 'io_addr'
>> not described in 'acrn_vdev'
>> acrn.h:479: warning: Excess struct member 'io_base' description in
>> 'acrn_vdev'
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> ---
>> Cc: Fei Li <fei1.li@intel.com>
>> Cc: acrn-dev@lists.projectacrn.org
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> ---
>> include/uapi/linux/acrn.h | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> --- linux-next-20251022.orig/include/uapi/linux/acrn.h
>> +++ linux-next-20251022/include/uapi/linux/acrn.h
>> @@ -420,12 +420,13 @@ struct acrn_pcidev {
>> /**
>> * struct acrn_mmiodev - Info for assigning or de-assigning a MMIO device
>> * @name: Name of the MMIO device.
>> - * @res[].user_vm_pa: Physical address of User VM of the MMIO
>> region
>> + * @res: MMIO resource descriptor info.
>
> Hi Randy
>
> Thanks for cooking this patch to help fix these warning.
> Could you just add the comment for `res` and keep the other comments for the fields of ` struct acrn_mmiodev ` ?
>
Do you mean leave the [] square brackets in the field name?
If that's what you mean, that's not valid kernel-doc notation.
>
>> + * @res.user_vm_pa: Physical address of User VM of the MMIO
>> region
>> * for the MMIO device.
>> - * @res[].service_vm_pa: Physical address of Service VM of the MMIO
>> + * @res.service_vm_pa: Physical address of Service VM of the
>> MMIO
>> * region for the MMIO device.
>> - * @res[].size: Size of the MMIO region for the MMIO
>> device.
>> - * @res[].mem_type: Memory type of the MMIO region for the
>> MMIO
>> + * @res.size: Size of the MMIO region for the MMIO
>> device.
>> + * @res.mem_type: Memory type of the MMIO region for the
>> MMIO
>> * device.
>> *
>> * This structure will be passed to hypervisor directly.
>> @@ -449,7 +450,7 @@ struct acrn_mmiodev {
>> * @id.fields.legacy_id: ID of the virtual device if not a PCI device
>> * @slot: Virtual Bus/Device/Function of the virtual
>> * device
>> - * @io_base: IO resource base address of the virtual device
>> + * @io_addr: IO resource base address of the virtual device
>> * @io_size: IO resource size of the virtual device
>> * @args: Arguments for the virtual device creation
>> *
--
~Randy
next prev parent reply other threads:[~2025-10-24 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 4:42 Randy Dunlap
2025-10-24 6:00 ` Li, Fei1
2025-10-24 6:06 ` Randy Dunlap [this message]
2025-10-24 6:22 ` Li, Fei1
2025-10-24 19:44 ` Randy Dunlap
2025-10-27 5:54 ` Li, Fei1
2025-10-27 6:11 ` Randy Dunlap
2025-10-28 3:19 ` Fei Li
2025-10-28 3:45 ` Randy Dunlap
2025-10-28 4:36 ` Fei Li
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=213c918b-b4aa-4174-af89-a4d17e8c30dc@infradead.org \
--to=rdunlap@infradead.org \
--cc=acrn-dev@lists.projectacrn.org \
--cc=fei1.li@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®