From: Rushil Gupta <rushilg@google.com>
To: Junfeng Guo <junfeng.guo@intel.com>
Cc: qi.z.zhang@intel.com, jingjing.wu@intel.com,
ferruh.yigit@xilinx.com, beilei.xing@intel.com, dev@dpdk.org,
jeroendb@google.com, jrkim@google.com, helin.zhang@intel.com
Subject: Re: [PATCH] maintainers: update for gve
Date: Wed, 9 Nov 2022 11:37:29 -0800 [thread overview]
Message-ID: <CANzqiF6LcjacJPY+x3Y3mZ=5R_V8Nmithp+-1ytt4HqkWSCUBA@mail.gmail.com> (raw)
In-Reply-To: <20221109072352.1387300-1-junfeng.guo@intel.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Thanks a lot Junfeng!
On Tue, Nov 8, 2022 at 11:26 PM Junfeng Guo <junfeng.guo@intel.com> wrote:
> Add co-maintainers from Google team for gve (Google Virtual Ethernet).
>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1c9922123e..d8c1d5272b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -698,6 +698,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: Jordan Kimbrough <jrkim@google.com>
> F: drivers/net/gve/
> F: doc/guides/nics/gve.rst
> F: doc/guides/nics/features/gve.ini
> --
> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 1456 bytes --]
next prev parent reply other threads:[~2022-11-10 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:23 Junfeng Guo
2022-11-09 19:37 ` Rushil Gupta [this message]
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 ` [PATCH v2] net/gve: add maintainers for GVE Junfeng Guo
2023-05-08 4:49 ` 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='CANzqiF6LcjacJPY+x3Y3mZ=5R_V8Nmithp+-1ytt4HqkWSCUBA@mail.gmail.com' \
--to=rushilg@google.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=helin.zhang@intel.com \
--cc=jeroendb@google.com \
--cc=jingjing.wu@intel.com \
--cc=jrkim@google.com \
--cc=junfeng.guo@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).