public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: John S <xaum.io@gmail.com>
To: mst@redhat.com, jasowang@redhat.com
Cc: xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	 virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH] virtio: add kernel-doc for map and vmap members
Date: Thu, 12 Mar 2026 22:42:39 +0100	[thread overview]
Message-ID: <CAAZVx9_Tq6afZJb-4pNKCwmB7xw=NZVCR8aSXM5N9+BbDdmTtg@mail.gmail.com> (raw)

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

             reply	other threads:[~2026-03-12 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 21:42 John S [this message]
2026-03-13  6:18 ` [PATCH] virtio: add kernel-doc for map and vmap members Jason Wang
2026-03-16 12:08   ` Krzysztof Kozlowski

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='CAAZVx9_Tq6afZJb-4pNKCwmB7xw=NZVCR8aSXM5N9+BbDdmTtg@mail.gmail.com' \
    --to=xaum.io@gmail.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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