From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jon Kohler <jon@nutanix.com>
Cc: jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, netdev@vger.kernel.org,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] MAINTAINERS: separate VIRTIO NET DRIVERS and add netdev
Date: Tue, 25 Nov 2025 19:04:34 -0500 [thread overview]
Message-ID: <20251125190356-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20251125210333.1594700-1-jon@nutanix.com>
On Tue, Nov 25, 2025 at 02:03:31PM -0700, Jon Kohler wrote:
> Changes to virtio network stack should be cc'd to netdev DL, separate
> it into its own group to add netdev in addition to virtualization DL.
>
> Signed-off-by: Jon Kohler <jon@nutanix.com>
> ---
> MAINTAINERS | 27 ++++++++++++++++++++-------
> 1 file changed, 20 insertions(+), 7 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e9a8d945632b..50cef0e5c7c8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -27139,29 +27139,23 @@ S: Maintained
> F: drivers/char/virtio_console.c
> F: include/uapi/linux/virtio_console.h
>
> -VIRTIO CORE AND NET DRIVERS
> +VIRTIO CORE
> M: "Michael S. Tsirkin" <mst@redhat.com>
> M: Jason Wang <jasowang@redhat.com>
> R: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> R: Eugenio Pérez <eperezma@redhat.com>
> L: virtualization@lists.linux.dev
> S: Maintained
> -F: Documentation/ABI/testing/sysfs-bus-vdpa
> -F: Documentation/ABI/testing/sysfs-class-vduse
> F: Documentation/devicetree/bindings/virtio/
> F: Documentation/driver-api/virtio/
> F: drivers/block/virtio_blk.c
> F: drivers/crypto/virtio/
> -F: drivers/net/virtio_net.c
> -F: drivers/vdpa/
> F: drivers/virtio/
> -F: include/linux/vdpa.h
> F: include/linux/virtio*.h
> F: include/linux/vringh.h
> F: include/uapi/linux/virtio_*.h
> F: net/vmw_vsock/virtio*
> F: tools/virtio/
> -F: tools/testing/selftests/drivers/net/virtio_net/
>
> VIRTIO CRYPTO DRIVER
> M: Gonglei <arei.gonglei@huawei.com>
> @@ -27273,6 +27267,25 @@ W: https://virtio-mem.gitlab.io/
> F: drivers/virtio/virtio_mem.c
> F: include/uapi/linux/virtio_mem.h
>
> +VIRTIO NET DRIVERS
> +M: "Michael S. Tsirkin" <mst@redhat.com>
> +M: Jason Wang <jasowang@redhat.com>
> +R: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> +R: Eugenio Pérez <eperezma@redhat.com>
> +L: netdev@vger.kernel.org
> +L: virtualization@lists.linux.dev
> +S: Maintained
> +F: Documentation/ABI/testing/sysfs-bus-vdpa
> +F: Documentation/ABI/testing/sysfs-class-vduse
> +F: drivers/net/virtio_net.c
> +F: drivers/vdpa/
> +F: include/linux/vdpa.h
> +F: include/linux/virtio_net.h
> +F: include/uapi/linux/vdpa.h
> +F: include/uapi/linux/vduse.h
> +F: include/uapi/linux/virtio_net.h
> +F: tools/testing/selftests/drivers/net/virtio_net/
> +
vdpa/vduse is more or a core thing.
Just split include/linux/virtio_net.h things away.
> VIRTIO PMEM DRIVER
> M: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
> L: virtualization@lists.linux.dev
> --
> 2.43.0
prev parent reply other threads:[~2025-11-26 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:03 [PATCH net-next] MAINTAINERS: separate VIRTIO NET DRIVERS and add netdev Jon Kohler
2025-11-26 0:04 ` Michael S. Tsirkin [this message]
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=20251125190356-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jon@nutanix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).