Re: [PATCH] virtio: document the map API in the driver writing guide

[Jonathan Corbet <corbet@lwn.net>]

John S <xaum.io@gmail.com> writes:

> 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>

So what is the story with "John S" in the From line?

Please, slow down with the AI-generated patches.  Perhaps focus on
exactly one of them, and get it to the point where it can be considered
for inclusion before doing any others?

jon