DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>,
	Shihong Wang <shihong.wang@nephogine.com>
Subject: RE: [PATCH 01/10] mailmap: update contributor entry
Date: Thu, 28 Sep 2023 01:50:13 +0000	[thread overview]
Message-ID: <SJ0PR13MB5545113457DCD7F1CA5D0FB99EC1A@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <4327de71-92f5-496a-a1be-dc6eac8deb8b@amd.com>

> On 9/25/2023 7:06 AM, Chaoyong He wrote:
> > From: Shihong Wang <shihong.wang@corigine.com>
> >
> > Add contributor entries to .mailmap file.
> >
> 
> .mailmap changes can be squashed to patch that introduces a new name, no
> need to have a separate patch for it. I can squash this while merging.
> 

Okay, I will do it in the v3 patch. Thanks!

> > Signed-off-by: Shihong Wang <shihong.wang@corigine.com>
> > Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> > ---
> >  .mailmap | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/.mailmap b/.mailmap
> > index 276325211c..5abd5810e2 100644
> > --- a/.mailmap
> > +++ b/.mailmap
> > @@ -200,6 +200,7 @@ Carolyn Wyborny <carolyn.wyborny@intel.com>
> > Chaeyong Chong <cychong@gmail.com>  Chaitanya Babu Talluri
> > <tallurix.chaitanya.babu@intel.com>
> >  Chandubabu Namburu <chandu@amd.com>
> > +Chang Miao <chang.miao@corigine.com>
> >  Changchun Ouyang <changchun.ouyang@intel.com>  Changpeng Liu
> > <changpeng.liu@intel.com>  Changqing Wu <changqingx.wu@intel.com> @@
> > -1265,6 +1266,7 @@ Shelton Chia <jiaxt@sinogrid.com>  Shepard Siegel
> > <shepard.siegel@atomicrules.com>  Shesha Sreenivasamurthy
> > <shesha@cisco.com>  Shibin Koikkara Reeny
> > <shibin.koikkara.reeny@intel.com>
> > +Shihong Wang <shihong.wang@corigine.com>
> >  Shijith Thotton <sthotton@marvell.com>
> > <shijith.thotton@caviumnetworks.com>
> >  Shiqi Liu <835703180@qq.com>
> >  Shiri Kuzin <shirik@nvidia.com> <shirik@mellanox.com>


  reply	other threads:[~2023-09-28  1:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  6:06 [PATCH 00/10] add the support of ipsec offload Chaoyong He
2023-09-25  6:06 ` [PATCH 01/10] mailmap: update contributor entry Chaoyong He
2023-09-27 14:19   ` Ferruh Yigit
2023-09-28  1:50     ` Chaoyong He [this message]
2023-09-25  6:06 ` [PATCH 02/10] net/nfp: add TLVs capability parsing Chaoyong He
2023-09-27 14:19   ` Ferruh Yigit
2023-09-28  2:02     ` Chaoyong He
2023-09-28  9:30       ` Ferruh Yigit
2023-09-25  6:06 ` [PATCH 03/10] net/nfp: add mailbox to support IPsec offload Chaoyong He
2023-09-25  6:06 ` [PATCH 04/10] net/nfp: initialize IPsec related content Chaoyong He
2023-09-25  6:06 ` [PATCH 05/10] net/nfp: get security capabilities and session size Chaoyong He
2023-09-25  6:06 ` [PATCH 06/10] net/nfp: get IPsec Rx/Tx packet statistics Chaoyong He
2023-09-25  6:06 ` [PATCH 07/10] net/nfp: create security session Chaoyong He
2023-09-25  6:06 ` [PATCH 08/10] net/nfp: update " Chaoyong He
2023-09-25  6:06 ` [PATCH 09/10] net/nfp: support IPsec Rx and Tx offload Chaoyong He
2023-09-25  6:06 ` [PATCH 10/10] net/nfp: destroy security session Chaoyong He
2023-09-26  2:49 ` [PATCH v2 00/10] add the support of ipsec offload Chaoyong He
2023-09-26  2:49   ` [PATCH v2 01/10] mailmap: update contributor entry Chaoyong He
2023-09-26  2:49   ` [PATCH v2 02/10] net/nfp: add TLVs capability parsing Chaoyong He
2023-09-26  2:49   ` [PATCH v2 03/10] net/nfp: add mailbox to support IPsec offload Chaoyong He
2023-09-26  2:49   ` [PATCH v2 04/10] net/nfp: initialize IPsec related content Chaoyong He
2023-09-26  2:49   ` [PATCH v2 05/10] net/nfp: get security capabilities and session size Chaoyong He
2023-09-26  2:49   ` [PATCH v2 06/10] net/nfp: get IPsec Rx/Tx packet statistics Chaoyong He
2023-09-26  2:49   ` [PATCH v2 07/10] net/nfp: create security session Chaoyong He
2023-09-26  2:49   ` [PATCH v2 08/10] net/nfp: update " Chaoyong He
2023-09-26  2:49   ` [PATCH v2 09/10] net/nfp: support IPsec Rx and Tx offload Chaoyong He
2023-09-26  2:49   ` [PATCH v2 10/10] net/nfp: destroy security session Chaoyong He
2023-09-27 14:20   ` [PATCH v2 00/10] add the support of ipsec offload Ferruh Yigit
2023-09-28  2:05     ` Chaoyong He
2023-09-28  9:33       ` Ferruh Yigit
2023-09-29  2:08   ` [PATCH v3 0/9] " Chaoyong He
2023-09-29  2:08     ` [PATCH v3 1/9] net/nfp: add TLVs capability parsing Chaoyong He
2023-09-29  2:08     ` [PATCH v3 2/9] net/nfp: add mailbox to support IPsec offload Chaoyong He
2023-09-29  2:08     ` [PATCH v3 3/9] net/nfp: initialize IPsec related content Chaoyong He
2023-09-29 10:00       ` Ferruh Yigit
2023-09-29  2:08     ` [PATCH v3 4/9] net/nfp: get security capabilities and session size Chaoyong He
2023-09-29  2:08     ` [PATCH v3 5/9] net/nfp: get IPsec Rx/Tx packet statistics Chaoyong He
2023-09-29  2:08     ` [PATCH v3 6/9] net/nfp: create security session Chaoyong He
2023-09-29  2:08     ` [PATCH v3 7/9] net/nfp: update " Chaoyong He
2023-09-29  2:08     ` [PATCH v3 8/9] net/nfp: support IPsec Rx and Tx offload Chaoyong He
2023-09-29  2:08     ` [PATCH v3 9/9] net/nfp: destroy security session Chaoyong He
2023-09-29 10:05     ` [PATCH v3 0/9] add the support of ipsec offload 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=SJ0PR13MB5545113457DCD7F1CA5D0FB99EC1A@SJ0PR13MB5545.namprd13.prod.outlook.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=oss-drivers@corigine.com \
    --cc=shihong.wang@nephogine.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).