DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Wenjun1" <wenjun1.wu@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Guo, Junfeng" <junfeng.guo@intel.com>,
	"Su, Simei" <simei.su@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: RE: [PATCH v1 2/3] maintainers: update for Intel ixgbe
Date: Thu, 21 Apr 2022 09:31:01 +0000	[thread overview]
Message-ID: <MN2PR11MB4565AED51A38018093B2CD78DFF49@MN2PR11MB4565.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MWHPR11MB1886CF159AE680888C4BCDEBE5F49@MWHPR11MB1886.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Yang, Qiming <qiming.yang@intel.com>
> Sent: Thursday, April 21, 2022 5:13 PM
> To: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Guo, Junfeng
> <junfeng.guo@intel.com>; Su, Simei <simei.su@intel.com>; Wu, Wenjun1
> <wenjun1.wu@intel.com>; Thomas Monjalon <thomas@monjalon.net>
> Subject: RE: [PATCH v1 2/3] maintainers: update for Intel ixgbe
> 
> > -----Original Message-----
> > From: Wang, Haiyue <haiyue.wang@intel.com>
> > Sent: 2022年4月8日 13:58
> > To: dev@dpdk.org
> > Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Yang, Qiming
> > <qiming.yang@intel.com>; Guo, Junfeng <junfeng.guo@intel.com>; Su,
> > Simei <simei.su@intel.com>; Wu, Wenjun1 <wenjun1.wu@intel.com>;
> Wang,
> > Haiyue <haiyue.wang@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>
> > Subject: [PATCH v1 2/3] maintainers: update for Intel ixgbe
> >
> > Qiming and Wenjun have been appointed the new maintainers for the
> > ixgbe PMD. Update the MAINTAINERS file to reflect this.
> >
> > Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> > ---
> >  MAINTAINERS | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS index 9d098161b2..513748b45b
> > 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -708,7 +708,8 @@ F: doc/guides/nics/features/e1000.ini
> >  F: doc/guides/nics/features/igb*.ini
> >
> >  Intel ixgbe
> > -M: Haiyue Wang <haiyue.wang@intel.com>
> > +M: Qiming Yang <qiming.yang@intel.com>
> > +M: Wenjun Wu <wenjun1.wu@intel.com>
> >  T: git://dpdk.org/next/dpdk-next-net-intel
> >  F: drivers/net/ixgbe/
> >  F: doc/guides/nics/ixgbe.rst
> > --
> > 2.35.1
> 
> Acked-by: Qiming Yang <qiming.yang@intel.com>

Acked-by: Wenjun Wu < wenjun1.wu@intel.com>

Thanks
Wenjun

  reply	other threads:[~2022-04-21  9:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  5:58 [PATCH v1 1/3] maintainers: update for Intel e1000 Haiyue Wang
2022-04-08  5:58 ` [PATCH v1 2/3] maintainers: update for Intel ixgbe Haiyue Wang
2022-04-21  9:13   ` Yang, Qiming
2022-04-21  9:31     ` Wu, Wenjun1 [this message]
2022-04-08  5:58 ` [PATCH v1 3/3] maintainers: update for Intel igc Haiyue Wang
2022-04-21  9:30   ` Su, Simei
2022-04-22  1:26     ` Guo, Junfeng
2022-04-21  9:19 ` [PATCH v1 1/3] maintainers: update for Intel e1000 Su, Simei
2022-04-21  9:30   ` Wu, Wenjun1
2022-05-10  9:18 ` Thomas Monjalon

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=MN2PR11MB4565AED51A38018093B2CD78DFF49@MN2PR11MB4565.namprd11.prod.outlook.com \
    --to=wenjun1.wu@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=junfeng.guo@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=simei.su@intel.com \
    --cc=thomas@monjalon.net \
    /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).