On Thu, Oct 15, 2026 at 11:40:49AM +0200, Eugenio Pérez wrote:
Several headers related to virtio, vDPA, VDUSE and vhost were not
covered by any specific MAINTAINERS entry and fell through to the
catch-all THE REST section:
- include/linux/device-id/virtio.h: not matched by the existing
"include/linux/virtio*.h" glob, which only matches files directly
under include/linux/ and does not recurse into subdirectories.
- include/uapi/linux/vdpa.h: the in-kernel include/linux/vdpa.h was
listed under VIRTIO CORE but its UAPI companion was missing; the
"include/uapi/linux/virtio_*.h" pattern does not match it because
the filename lacks the "virtio_" prefix.
Maybe we should tell to the agent to avoid useless info in the commit
message, I mean it's pretty clear that "include/uapi/linux/virtio_*.h"
will not match include/uapi/linux/vdpa.h ...
- include/uapi/linux/vduse.h: there is no dedicated VDUSE section in
MAINTAINERS; the driver lives under drivers/vdpa/ which is already
covered by VIRTIO CORE, so the UAPI header belongs there too.
- include/uapi/linux/vhost_types.h: the VIRTIO HOST (VHOST) section
explicitly lists include/uapi/linux/vhost.h but omits its companion
types header.
Assisted-by: claude-sonnet 4.6
nit: the suggested tag in Documentation/process/coding-assistants.rst is
Assisted-by: LLM [TOOL1] [TOOL2]
Signed-off-by: Eugenio Pérez <[email protected]>
---
MAINTAINERS | 4 ++++
1 file changed, 4 insertions(+)
Anyway, the patch LGTM:
Reviewed-by: Stefano Garzarella <[email protected]>
Maybe to be fixed in another patch, LLM here found also others files
related to virtio/vhost/vdpa uncovered:
Other virtio-related files not covered by any virtio/vhost/vdpa
MAINTAINERS entry:
- Documentation/ABI/testing/sysfs-fs-virtiofs
Current: no section (THE REST only)
Suggested: VIRTIO FILE SYSTEM
- Documentation/userspace-api/vduse.rst
Current: DOCUMENTATION only
Suggested: VIRTIO CORE (already lists sysfs-class-vduse)
- include/trace/events/vsock_virtio_transport_common.h
Current: TRACING only
Suggested: VIRTIO AND VHOST VSOCK DRIVER
(next to virtio_transport_common.c)
- drivers/nvdimm/virtio_pmem.h
Current: LIBNVDIMM only
Suggested: VIRTIO PMEM DRIVER (lists virtio_pmem.c and
nd_virtio.c, but not the header)
- Documentation/devicetree/bindings/gpio/gpio-virtio.yaml
Current: GPIO + DT bindings
Suggested: VIRTIO GPIO DRIVER
- Documentation/devicetree/bindings/i2c/i2c-virtio.yaml
Current: I2C + DT bindings
Suggested: VIRTIO I2C DRIVER
- Documentation/networking/device_drivers/ethernet/amd/pds_vdpa.rst
Current: NETWORKING + DOCUMENTATION
Suggested: PDS DSC VIRTIO DATA PATH ACCELERATOR
(only lists drivers/vdpa/pds/)
- include/linux/mlx5/mlx5_ifc_vdpa.h
Current: MLX5 core/IB only
Suggested: possibly MELLANOX MLX5 VDPA DRIVER (debatable, it's an
mlx5 interface header)
I'll send a fix for the vsock events.
Thanks,
Stefano
