public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: John S <xaum.io@gmail.com>, mst@redhat.com, jasowang@redhat.com
Cc: xuanzhuo@linux.alibaba.com, eperezma@redhat.com, corbet@lwn.net,
	skhan@linuxfoundation.org, virtualization@lists.linux.dev,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virtio: document the map API in the driver writing guide
Date: Mon, 16 Mar 2026 13:06:00 +0100	[thread overview]
Message-ID: <085ebc8c-636b-45d6-8431-878cbe90314b@kernel.org> (raw)
In-Reply-To: <CAAZVx999y-DvB7Dp2ekoHk6s8aqqScd2gKSY4ySGAK6NNXeH5g@mail.gmail.com>

On 12/03/2026 22:58, John S wrote:
> Add a new "Buffer mapping" section to the virtio driver writing guide
> documenting the virtio map API (struct virtio_map_ops). This API was
> introduced in commit bee8c7c24b73 ("virtio: introduce map ops in virtio
> core") to allow transports and devices that do not perform DMA (such
> as VDUSE) to provide their own buffer mapping logic instead of abusing
> the DMA API.
> 
> The new section explains when and why custom map ops are used, documents
> the virtio_map_ops structure and the union virtio_map token, and
> references the driver-facing mapping helpers with their kernel-doc.
> 
> Signed-off-by: Kit Dallege <xaum.io@gmail.com>
> ---
>  .../virtio/writing_virtio_drivers.rst         | 72 +++++++++++++++++++
>  1 file changed, 72 insertions(+)

NAK, because:
1. Mismatched DCO or anonymous contribution
2. Likely unverified LLM microslop

Best regards,
Krzysztof

  parent reply	other threads:[~2026-03-16 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 21:58 [PATCH] virtio: document the map API in the driver writing guide John S
2026-03-13  6:18 ` Jason Wang
2026-03-16 12:06 ` Krzysztof Kozlowski [this message]
2026-03-17 14:49 ` Jonathan Corbet

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=085ebc8c-636b-45d6-8431-878cbe90314b@kernel.org \
    --to=krzk@kernel.org \
    --cc=corbet@lwn.net \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=skhan@linuxfoundation.org \
    --cc=virtualization@lists.linux.dev \
    --cc=xaum.io@gmail.com \
    --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