From: Junfeng Guo <junfeng.guo@intel.com>
To: qi.z.zhang@intel.com, jingjing.wu@intel.com,
ferruh.yigit@amd.com, beilei.xing@intel.com
Cc: dev@dpdk.org, Junfeng Guo <junfeng.guo@intel.com>
Subject: [PATCH v2 3/3] net/gve: add maintainers for GVE
Date: Tue, 28 Mar 2023 17:28:43 +0800 [thread overview]
Message-ID: <20230328092843.1775431-4-junfeng.guo@intel.com> (raw)
In-Reply-To: <20230328092843.1775431-1-junfeng.guo@intel.com>
Add maintainers from Google for GVE.
Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1a33ad8592..988c7aecfa 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -714,6 +714,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-03-28 9:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 2:08 [PATCH 0/2] update license and copyright Junfeng Guo
2023-03-28 2:08 ` [PATCH 1/2] net/gve: switch copyright from MIT to BSD-3 Junfeng Guo
2023-03-28 8:51 ` Ferruh Yigit
2023-03-28 8:57 ` Guo, Junfeng
2023-03-28 8:55 ` Ferruh Yigit
2023-03-28 9:06 ` Guo, Junfeng
2023-03-28 9:09 ` Ferruh Yigit
2023-03-28 9:35 ` Guo, Junfeng
2023-03-28 2:08 ` [PATCH 2/2] net/gve: update copyright holders Junfeng Guo
2023-03-28 8:56 ` Ferruh Yigit
2023-03-28 9:35 ` Guo, Junfeng
2023-03-28 10:10 ` Ferruh Yigit
2023-03-29 14:07 ` Thomas Monjalon
2023-03-30 7:20 ` Guo, Junfeng
2023-03-30 13:14 ` Thomas Monjalon
2023-03-30 15:18 ` Rushil Gupta
2023-03-30 15:26 ` Rushil Gupta
2023-03-31 2:32 ` Guo, Junfeng
2023-03-28 9:28 ` [PATCH v2 0/3] update license and " Junfeng Guo
2023-03-28 9:28 ` [PATCH v2 1/3] net/gve: switch license from MIT to BSD-3 Junfeng Guo
2023-03-28 9:28 ` [PATCH v2 2/3] net/gve: update copyright holders Junfeng Guo
2023-03-28 9:28 ` Junfeng Guo [this message]
2023-03-28 9:45 ` [PATCH v3 0/3] update license and " Junfeng Guo
2023-03-28 9:45 ` [PATCH v3 1/3] net/gve: switch license from MIT to BSD-3 Junfeng Guo
2023-03-28 10:36 ` Ferruh Yigit
2023-03-29 2:35 ` Guo, Junfeng
2023-03-28 9:45 ` [PATCH v3 2/3] net/gve: update copyright holders Junfeng Guo
2023-03-28 10:37 ` Ferruh Yigit
2023-03-28 22:11 ` Rushil Gupta
2023-03-28 9:45 ` [PATCH v3 3/3] net/gve: add maintainers for GVE Junfeng Guo
2023-03-28 10:00 ` Guo, Junfeng
2023-03-28 10:34 ` Ferruh Yigit
2023-03-29 2:54 ` Guo, Junfeng
2023-03-29 2:26 ` [PATCH v4 0/3] update license and copyright holders Junfeng Guo
2023-03-29 2:27 ` [PATCH v4 1/3] net/gve: switch license from MIT to BSD-3 Junfeng Guo
2023-03-29 8:08 ` Ferruh Yigit
2023-03-29 2:27 ` [PATCH v4 2/3] net/gve: update copyright holders Junfeng Guo
2023-03-29 2:27 ` [PATCH v4 3/3] net/gve: add maintainers for GVE Junfeng Guo
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=20230328092843.1775431-4-junfeng.guo@intel.com \
--to=junfeng.guo@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.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).