All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Virtualization" <virtualization@lists.linux.dev>,
	"Jason Wang" <jasowang@redhat.com>,
	"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>
Subject: Re: [PATCH v2] virtio: Describe @map and @vmap members in virtio_device struct
Date: Fri, 26 Dec 2025 14:13:00 -0500	[thread overview]
Message-ID: <20251226140725-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20251219031647.25264-1-bagasdotme@gmail.com>

On Fri, Dec 19, 2025 at 10:16:47AM +0700, Bagas Sanjaya wrote:
> Sphinx reports kernel-doc warnings:
> 
> WARNING: ./include/linux/virtio.h:181 struct member 'map' not described in 'virtio_device'
> WARNING: ./include/linux/virtio.h:181 struct member 'vmap' not described in 'virtio_device'
> 
> Describe these members.
> 
> Fixes: bee8c7c24b7373 ("virtio: introduce map ops in virtio core")
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Acked-by: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>


Well I was going to apply and now I have second thoughts.
The patch does describe the members, it just does not
describe them well.
for example,


> ---
> This patch is split from kernel-doc fixup series [1].
> 
> Changes since v1 [2]:
> 
>   - Apply review trailers (Michael, Jason)
> 
> [1]: https://lore.kernel.org/lkml/20251215113903.46555-1-bagasdotme@gmail.com/
> [2]: https://lore.kernel.org/lkml/20251215113903.46555-7-bagasdotme@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 132a474e59140a..68ead8fda9c921 100644
> --- a/include/linux/virtio.h
> +++ b/include/linux/virtio.h
> @@ -150,11 +150,13 @@ struct virtio_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: configuration ops for device's mapping buffer

there's no "mapping buffer" that needs configuration.
the type tells it all:
 * struct virtio_map_ops - operations for mapping buffer for a virtio 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: device virtual map

this one is not a "virtual map" either.
more a "device or domain used for mapping memory"

>   * @debugfs_dir: debugfs directory entry.
>   * @debugfs_filter_features: features to be filtered set by debugfs.
>   */
> 
> base-commit: ea1013c1539270e372fc99854bc6e4d94eaeff66
> -- 
> An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2025-12-26 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19  3:16 [PATCH v2] virtio: Describe @map and @vmap members in virtio_device struct Bagas Sanjaya
2025-12-26 19:13 ` Michael S. Tsirkin [this message]
2025-12-27 22:57   ` Bagas Sanjaya

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=20251226140725-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=bagasdotme@gmail.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.