From: "Griffin, John" <john.griffin@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] maintainers: update for qat and ipsec-mb pmds
Date: Thu, 20 May 2021 09:50:25 +0000 [thread overview]
Message-ID: <DM6PR11MB34047586EA34FB40EAC4506C992A9@DM6PR11MB3404.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210520094710.147945-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Sent: Thursday, May 20, 2021 10:47 AM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; gakhil@marvell.com; Yigit, Ferruh
> <ferruh.yigit@intel.com>; Doherty, Declan <declan.doherty@intel.com>;
> Griffin, John <john.griffin@intel.com>; Jain, Deepak K
> <deepak.k.jain@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; Zhang,
> Roy Fan <roy.fan.zhang@intel.com>
> Subject: [dpdk-dev] maintainers: update for qat and ipsec-mb pmds
>
> Add myself to Crypto API, QAT, SW PMDs based on ipsec-mb, and NULL PMD
> maintainer.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> MAINTAINERS | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5877a16971..11653b3dcd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -421,7 +421,7 @@ F: examples/bbdev_app/
> F: doc/guides/sample_app_ug/bbdev_app.rst
>
> Crypto API
> -M: Declan Doherty <declan.doherty@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> T: git://dpdk.org/next/dpdk-next-crypto
> F: lib/cryptodev/
> F: app/test/test_cryptodev*
> @@ -429,7 +429,7 @@ F: examples/l2fwd-crypto/
>
> Security API
> M: Akhil Goyal <gakhil@marvell.com>
> -M: Declan Doherty <declan.doherty@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> T: git://dpdk.org/next/dpdk-next-crypto
> F: lib/security/
> F: doc/guides/prog_guide/rte_security.rst
> @@ -1031,23 +1031,22 @@ F: drivers/crypto/scheduler/
> F: doc/guides/cryptodevs/scheduler.rst
>
> Intel AES-NI GCM
> -M: Declan Doherty <declan.doherty@intel.com>
> M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/aesni_gcm/
> F: doc/guides/cryptodevs/aesni_gcm.rst
> F: doc/guides/cryptodevs/features/aesni_gcm.ini
>
> Intel AES-NI Multi-Buffer
> -M: Declan Doherty <declan.doherty@intel.com>
> M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/aesni_mb/
> F: doc/guides/cryptodevs/aesni_mb.rst
> F: doc/guides/cryptodevs/features/aesni_mb.ini
>
> Intel QuickAssist
> -M: John Griffin <john.griffin@intel.com>
> M: Fiona Trahe <fiona.trahe@intel.com>
> -M: Deepak Kumar Jain <deepak.k.jain@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/qat/
> F: drivers/common/qat/
> F: doc/guides/cryptodevs/qat.rst
> @@ -1055,6 +1054,7 @@ F: doc/guides/cryptodevs/features/qat.ini
>
> KASUMI
> M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/kasumi/
> F: doc/guides/cryptodevs/kasumi.rst
> F: doc/guides/cryptodevs/features/kasumi.ini
> @@ -1081,7 +1081,7 @@ F: doc/guides/cryptodevs/octeontx2.rst
> F: doc/guides/cryptodevs/features/octeontx2.ini
>
> Null Crypto
> -M: Declan Doherty <declan.doherty@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/null/
> F: doc/guides/cryptodevs/null.rst
> F: doc/guides/cryptodevs/features/null.ini
> @@ -1108,13 +1108,14 @@ F: doc/guides/cryptodevs/dpaa2_sec.rst
> F: doc/guides/cryptodevs/features/dpaa2_sec.ini
>
> OpenSSL
> -M: Declan Doherty <declan.doherty@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/openssl/
> F: doc/guides/cryptodevs/openssl.rst
> F: doc/guides/cryptodevs/features/openssl.ini
>
> SNOW 3G
> M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/snow3g/
> F: doc/guides/cryptodevs/snow3g.rst
> F: doc/guides/cryptodevs/features/snow3g.ini
> @@ -1127,6 +1128,7 @@ F: doc/guides/cryptodevs/features/virtio.ini
>
> ZUC
> M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> +M: Fan Zhang <roy.fan.zhang@intel.com>
> F: drivers/crypto/zuc/
> F: doc/guides/cryptodevs/zuc.rst
> F: doc/guides/cryptodevs/features/zuc.ini
> --
> 2.25.1
Acked-by: John Griffin <john.griffin@intel.com>
next prev parent reply other threads:[~2021-05-20 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 9:47 Fan Zhang
2021-05-20 9:50 ` Griffin, John [this message]
2021-05-20 10:57 ` Doherty, Declan
2021-05-20 11:04 ` Trahe, Fiona
2021-05-20 12:16 ` [dpdk-dev] [dpdk-dev v2] " Fan Zhang
2021-05-20 13:01 ` Thomas Monjalon
2021-05-21 9:03 ` Zhang, Roy Fan
2021-05-21 9:23 ` [dpdk-dev] [dpdk-dev v3] maintainers: update for crypto api/crypto perf/sw crypto pmds using ipsec-mb Fan Zhang
2021-05-21 11:18 ` De Lara Guarch, Pablo
2021-06-29 20:31 ` [dpdk-dev] [EXT] " Akhil Goyal
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=DM6PR11MB34047586EA34FB40EAC4506C992A9@DM6PR11MB3404.namprd11.prod.outlook.com \
--to=john.griffin@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=gakhil@marvell.com \
--cc=roy.fan.zhang@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).