From: Thomas Monjalon <thomas@monjalon.net>
To: Junfeng Guo <junfeng.guo@intel.com>
Cc: dev@dpdk.org, 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,
Rushil Gupta <rushilg@google.com>,
Jeroen de Borst <jeroendb@google.com>,
Jordan Kimbrough <jrkim@google.com>
Subject: Re: [PATCH] maintainers: update for gve
Date: Tue, 15 Nov 2022 09:33:26 +0100 [thread overview]
Message-ID: <2605325.BddDVKsqQX@thomas> (raw)
In-Reply-To: <CANzqiF6LcjacJPY+x3Y3mZ=5R_V8Nmithp+-1ytt4HqkWSCUBA@mail.gmail.com>
09/11/2022 20:37, Rushil Gupta:
> 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>
> > ---
> > 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>
They were not part of the patch review process in the mailing list,
why do you want them to become maintainers?
I think it would be saner to have them involved first.
next prev parent reply other threads:[~2022-11-15 8:33 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 [this message]
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=2605325.BddDVKsqQX@thomas \
--to=thomas@monjalon.net \
--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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.