DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Rushil Gupta <rushilg@google.com>, Junfeng Guo <junfeng.guo@intel.com>
Cc: qi.z.zhang@intel.com, dev@dpdk.org,
	Jeroen de Borst <jeroendb@google.com>,
	Joshua Washington <joshwash@google.com>
Subject: Re: [PATCH v2] net/gve: add maintainers for GVE
Date: Mon, 8 May 2023 18:44:58 +0100	[thread overview]
Message-ID: <34879b29-9615-5e69-ba7e-e088e14df238@amd.com> (raw)
In-Reply-To: <CANzqiF48-OKXSDrfALDFdKsLnLHVXZPs-7-k8F=QAX5W9g7kvw@mail.gmail.com>

>> On 5/8/2023 5:49 AM, Rushil Gupta wrote:

Moved and accumulated acks down.

>> 
>>> On Thu, May 4, 2023 at 7:19 PM Junfeng Guo <junfeng.guo@intel.com> wrote:
>>>>
>>>> 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>> 
>>>
>>> acked-by: Rushil Gupta <rushilg@google.com>
>>> 
>> 
>> acked-by: Joshua Washington <joshwash@google.com>
>>
>
> acked-by: Jeroen de Borst <jeroendb@google.com>
>

Applied to dpdk-next-net/main, thanks.

      parent reply	other threads:[~2023-05-08 17:45 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 ` [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 [this message]

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=34879b29-9615-5e69-ba7e-e088e14df238@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=jeroendb@google.com \
    --cc=joshwash@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 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).