DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Guo, Jia" <jia.guo@intel.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>,
	"Wang, Haiyue" <haiyue.wang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v1] maintainers: update for igb igc ixgbe
Date: Mon, 7 Sep 2020 05:59:03 +0000	[thread overview]
Message-ID: <737dbf202d1e452597de4a7fd53e1386@intel.com> (raw)
In-Reply-To: <MWHPR11MB20139BAB4BBBE2B2C89BA454B7280@MWHPR11MB2013.namprd11.prod.outlook.com>

Acked-by: Jeff Guo <jia.guo@intel.com>

-----Original Message-----
From: Zhao1, Wei <wei.zhao1@intel.com> 
Sent: Monday, September 7, 2020 11:32 AM
To: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org
Cc: Guo, Jia <jia.guo@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Thomas Monjalon <thomas@monjalon.net>
Subject: RE: [PATCH v1] maintainers: update for igb igc ixgbe

Acked-by: Wei Zhao <wei.zhao1@intel.com>

> -----Original Message-----
> From: Wang, Haiyue <haiyue.wang@intel.com>
> Sent: Monday, September 7, 2020 11:19 AM
> To: dev@dpdk.org
> Cc: Zhao1, Wei <wei.zhao1@intel.com>; Guo, Jia <jia.guo@intel.com>; 
> Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Haiyue 
> <haiyue.wang@intel.com>; Thomas Monjalon <thomas@monjalon.net>
> Subject: [PATCH v1] maintainers: update for igb igc ixgbe
> 
> Co-work with Jeff, setting me as new maintainer for igb, igc and ixgbe.
> 
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> ---
>  MAINTAINERS | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS index ed163f5d5..96cf04c72 
> 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -670,8 +670,8 @@ F: doc/guides/nics/hinic.rst
>  F: doc/guides/nics/features/hinic.ini
> 
>  Intel e1000
> -M: Wei Zhao <wei.zhao1@intel.com>
>  M: Jeff Guo <jia.guo@intel.com>
> +M: Haiyue Wang <haiyue.wang@intel.com>
>  T: git://dpdk.org/next/dpdk-next-net-intel
>  F: drivers/net/e1000/
>  F: doc/guides/nics/e1000em.rst
> @@ -680,8 +680,8 @@ F: doc/guides/nics/features/e1000.ini
>  F: doc/guides/nics/features/igb*.ini
> 
>  Intel ixgbe
> -M: Wei Zhao <wei.zhao1@intel.com>
>  M: Jeff Guo <jia.guo@intel.com>
> +M: Haiyue Wang <haiyue.wang@intel.com>
>  T: git://dpdk.org/next/dpdk-next-net-intel
>  F: drivers/net/ixgbe/
>  F: doc/guides/nics/ixgbe.rst
> @@ -722,8 +722,8 @@ F: doc/guides/nics/ice.rst
>  F: doc/guides/nics/features/ice.ini
> 
>  Intel igc
> -M: Wei Zhao <wei.zhao1@intel.com>
>  M: Jeff Guo <jia.guo@intel.com>
> +M: Haiyue Wang <haiyue.wang@intel.com>
>  T: git://dpdk.org/next/dpdk-next-net-intel
>  F: drivers/net/igc/
>  F: doc/guides/nics/igc.rst
> --
> 2.28.0



  reply	other threads:[~2020-09-07  5:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  3:18 Haiyue Wang
2020-09-07  3:31 ` Zhao1, Wei
2020-09-07  5:59   ` Guo, Jia [this message]
2020-09-14 13:12     ` 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=737dbf202d1e452597de4a7fd53e1386@intel.com \
    --to=jia.guo@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=thomas@monjalon.net \
    --cc=wei.zhao1@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).