From: Junfeng Guo <junfeng.guo@intel.com>
To: qi.z.zhang@intel.com, ferruh.yigit@amd.com
Cc: dev@dpdk.org, Junfeng Guo <junfeng.guo@intel.com>,
Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>,
Joshua Washington <joshwash@google.com>
Subject: [PATCH v2] net/gve: add maintainers for GVE
Date: Fri, 5 May 2023 10:18:53 +0800 [thread overview]
Message-ID: <20230505021853.508660-1-junfeng.guo@intel.com> (raw)
In-Reply-To: <20221109072352.1387300-1-junfeng.guo@intel.com>
Add maintainers from Google for GVE.
Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
Signed-off-by: Jeroen de Borst <jeroendb@google.com>
Signed-off-by: Rushil Gupta <rushilg@google.com>
Signed-off-by: Joshua Washington <joshwash@google.com>
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8df23e5099..08001751b0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -713,6 +713,9 @@ F: doc/guides/nics/features/enic.ini
Google Virtual Ethernet
M: Junfeng Guo <junfeng.guo@intel.com>
+M: Jeroen de Borst <jeroendb@google.com>
+M: Rushil Gupta <rushilg@google.com>
+M: Joshua Washington <joshwash@google.com>
F: drivers/net/gve/
F: doc/guides/nics/gve.rst
F: doc/guides/nics/features/gve.ini
--
2.34.1
next prev parent reply other threads:[~2023-05-05 2:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:23 [PATCH] maintainers: update for gve Junfeng Guo
2022-11-09 19:37 ` Rushil Gupta
2022-11-15 8:33 ` Thomas Monjalon
2022-11-15 9:22 ` Guo, Junfeng
2022-11-15 20:04 ` Rushil Gupta
2022-11-15 20:54 ` Jordan Kimbrough
2022-11-15 23:43 ` Jeroen de Borst
2023-05-05 2:18 ` Junfeng Guo [this message]
2023-05-08 4:49 ` [PATCH v2] net/gve: add maintainers for GVE Rushil Gupta
2023-05-08 15:26 ` Joshua Washington
2023-05-08 15:42 ` Jeroen de Borst
2023-05-08 17:44 ` Ferruh Yigit
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=20230505021853.508660-1-junfeng.guo@intel.com \
--to=junfeng.guo@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=qi.z.zhang@intel.com \
--cc=rushilg@google.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).