From: Bobby Eshleman <bobbyeshleman@meta.com>
To: <netdev@vger.kernel.org>, <virtualization@lists.linux.dev>,
<kvm@vger.kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@kernel.org>,
Stefano Garzarella <sgarzare@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
<linux-kernel@vger.kernel.org>,
Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: Bobby Eshleman <bobbyeshleman@meta.com>
Subject: [PATCH net] MAINTAINERS: add Bobby Eshleman as vsock reviewer
Date: Mon, 12 Oct 2026 12:58:08 -0700 [thread overview]
Message-ID: <20261012-add-maintainers-v1-1-ef0488f460db@meta.com> (raw)
I've been reviewing vsock via lore+lei for a while now.
Finally adding myself as a formal reviewer, since vsock will continue
being stuck with me for the foreseeable future.
Signed-off-by: Bobby Eshleman <bobbyeshleman@meta.com>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f53047aa8d3c..cc1341f6e15c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -28840,6 +28840,7 @@ F: virt/lib/
VIRTIO AND VHOST VSOCK DRIVER
M: Stefan Hajnoczi <stefanha@redhat.com>
M: Stefano Garzarella <sgarzare@redhat.com>
+R: Bobby Eshleman <bobbyeshleman@meta.com>
L: kvm@vger.kernel.org
L: virtualization@lists.linux.dev
L: netdev@vger.kernel.org
@@ -29145,6 +29146,7 @@ F: drivers/media/test-drivers/vivid/*
VM SOCKETS (AF_VSOCK)
M: Stefano Garzarella <sgarzare@redhat.com>
+R: Bobby Eshleman <bobbyeshleman@meta.com>
L: virtualization@lists.linux.dev
L: netdev@vger.kernel.org
S: Maintained
---
base-commit: 8e2fbe0e75d38690d551456658194c632933cb57
change-id: 20261012-add-maintainers-bc6e8a6fa68b
Best regards,
--
Bobby Eshleman <bobbyeshleman@meta.com>
next reply other threads:[~2026-10-12 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 19:58 Bobby Eshleman [this message]
2026-10-13 9:18 ` [PATCH net] MAINTAINERS: add Bobby Eshleman as vsock reviewer Stefano Garzarella
2026-10-13 10:17 ` Michael S. Tsirkin
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=20261012-add-maintainers-v1-1-ef0488f460db@meta.com \
--to=bobbyeshleman@meta.com \
--cc=bobbyeshleman@gmail.com \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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