* [PATCH] virtio: add kernel-doc for map and vmap members
@ 2026-03-12 21:42 John S
2026-03-13 6:18 ` Jason Wang
0 siblings, 1 reply; 3+ messages in thread
From: John S @ 2026-03-12 21:42 UTC (permalink / raw)
To: mst, jasowang; +Cc: xuanzhuo, eperezma, virtualization, linux-kernel
Document the map and vmap members of struct virtio_device that were
added without kernel-doc descriptions.
This fixes the following warnings when building with W=1:
include/linux/virtio.h: struct member 'map' not described in 'virtio_device'
include/linux/virtio.h: struct member 'vmap' not described in 'virtio_device'
Signed-off-by: Kit Dallege <xaum.io@gmail.com>
---
include/linux/virtio.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
index 3386a4a8d06b..fc7940298d4b 100644
--- a/include/linux/virtio.h
+++ b/include/linux/virtio.h
@@ -157,10 +157,12 @@ struct virtio_device_admin_cmd {
* @id: the device type identification (used to match it with a driver).
* @config: the configuration ops for this device.
* @vringh_config: configuration ops for host vrings.
+ * @map: the mapping ops for this device.
* @vqs: the list of virtqueues for this device.
* @features: the 64 lower features supported by both driver and device.
* @features_array: the full features space supported by both driver and
* device.
* @priv: private pointer for the driver's use.
+ * @vmap: mapping token passed to the mapping operations.
* @debugfs_dir: debugfs directory entry.
* @debugfs_filter_features: features to be filtered set by debugfs.
*/
--
2.53.0
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH] virtio: add kernel-doc for map and vmap members
2026-03-12 21:42 [PATCH] virtio: add kernel-doc for map and vmap members John S
@ 2026-03-13 6:18 ` Jason Wang
2026-03-16 12:08 ` Krzysztof Kozlowski
0 siblings, 1 reply; 3+ messages in thread
From: Jason Wang @ 2026-03-13 6:18 UTC (permalink / raw)
To: John S; +Cc: mst, xuanzhuo, eperezma, virtualization, linux-kernel
On Fri, Mar 13, 2026 at 5:42 AM John S <xaum.io@gmail.com> wrote:
>
> Document the map and vmap members of struct virtio_device that were
> added without kernel-doc descriptions.
>
> This fixes the following warnings when building with W=1:
>
> include/linux/virtio.h: struct member 'map' not described in 'virtio_device'
> include/linux/virtio.h: struct member 'vmap' not described in 'virtio_device'
>
> Signed-off-by: Kit Dallege <xaum.io@gmail.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Thanks
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] virtio: add kernel-doc for map and vmap members
2026-03-13 6:18 ` Jason Wang
@ 2026-03-16 12:08 ` Krzysztof Kozlowski
0 siblings, 0 replies; 3+ messages in thread
From: Krzysztof Kozlowski @ 2026-03-16 12:08 UTC (permalink / raw)
To: Jason Wang, John S; +Cc: mst, xuanzhuo, eperezma, virtualization, linux-kernel
On 13/03/2026 07:18, Jason Wang wrote:
> On Fri, Mar 13, 2026 at 5:42 AM John S <xaum.io@gmail.com> wrote:
>>
>> Document the map and vmap members of struct virtio_device that were
>> added without kernel-doc descriptions.
>>
>> This fixes the following warnings when building with W=1:
>>
>> include/linux/virtio.h: struct member 'map' not described in 'virtio_device'
>> include/linux/virtio.h: struct member 'vmap' not described in 'virtio_device'
>>
>> Signed-off-by: Kit Dallege <xaum.io@gmail.com>
>
> Acked-by: Jason Wang <jasowang@redhat.com>
>
Sorry, but no :(.
Patch has incorrect DCO chain and most likely is product of LLM
microslop without proper marking (as the rest of author's
contributions). Therefore this should be actually reviewed before accepting.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-03-16 12:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-12 21:42 [PATCH] virtio: add kernel-doc for map and vmap members John S
2026-03-13 6:18 ` Jason Wang
2026-03-16 12:08 ` Krzysztof Kozlowski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox