From: Akhil Goyal <gakhil@marvell.com>
To: <dev@dpdk.org>, <thomas@monjalon.net>
Cc: <ferruh.yigit@intel.com>, <jerinj@marvell.com>,
<bluca@debian.org>, <ktraynor@redhat.com>,
<bruce.richardson@intel.com>, <ruifeng.wang@arm.com>,
<honnappa.nagarahalli@arm.com>, <konstantin.ananyev@intel.com>,
<nicolas.chautru@intel.com>, <declan.doherty@intel.com>,
<fiona.trahe@intel.com>, <abhinandan.gujjar@intel.com>,
<hemant.agrawal@nxp.com>, <nipun.gupta@nxp.com>,
<sachin.saxena@oss.nxp.com>, <anoobj@marvell.com>,
<matan@nvidia.com>, <asomalap@amd.com>,
<ajit.khaparde@broadcom.com>, <roy.fan.zhang@intel.com>,
<pablo.de.lara.guarch@intel.com>, <michaelsh@marvell.com>,
<g.singh@nxp.com>, <jianjay.zhou@huawei.com>,
<ashish.gupta@marvell.com>, <lee.daly@intel.com>,
<ssahu@marvell.com>, <ciara.power@intel.com>,
<radu.nicolau@intel.com>, <john.mcnamara@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: [dpdk-dev] [PATCH] maintainers: update crypto ownership
Date: Tue, 23 Feb 2021 14:12:49 +0530 [thread overview]
Message-ID: <20210223084249.90931-1-gakhil@marvell.com> (raw)
Recently joined Marvell, hence change in
email id for crypto sub tree, security API
and ipsec-secgw application maintainers list.
Signed-off-by: Akhil Goyal <gakhil@marvell.com>
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1962284e9..78e91faf9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -54,7 +54,7 @@ M: Chenbo Xia <chenbo.xia@intel.com>
T: git://dpdk.org/next/dpdk-next-virtio
Next-crypto Tree
-M: Akhil Goyal <akhil.goyal@nxp.com>
+M: Akhil Goyal <gakhil@marvell.com>
T: git://dpdk.org/next/dpdk-next-crypto
Next-eventdev Tree
@@ -424,7 +424,7 @@ F: app/test/test_cryptodev*
F: examples/l2fwd-crypto/
Security API
-M: Akhil Goyal <akhil.goyal@nxp.com>
+M: Akhil Goyal <gakhil@marvell.com>
M: Declan Doherty <declan.doherty@intel.com>
T: git://dpdk.org/next/dpdk-next-crypto
F: lib/librte_security/
@@ -1642,7 +1642,7 @@ F: doc/guides/sample_app_ug/hello_world.rst
IPsec security gateway example
M: Radu Nicolau <radu.nicolau@intel.com>
-M: Akhil Goyal <akhil.goyal@nxp.com>
+M: Akhil Goyal <gakhil@marvell.com>
F: examples/ipsec-secgw/
F: doc/guides/sample_app_ug/ipsec_secgw.rst
--
2.25.1
next reply other threads:[~2021-02-23 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 8:42 Akhil Goyal [this message]
2021-02-23 9:40 ` Thomas Monjalon
2021-02-23 9:45 ` Hemant Agrawal
2021-02-23 10:45 ` Thomas Monjalon
2021-02-23 9:44 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=20210223084249.90931-1-gakhil@marvell.com \
--to=gakhil@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anoobj@marvell.com \
--cc=ashish.gupta@marvell.com \
--cc=asomalap@amd.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=jianjay.zhou@huawei.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=lee.daly@intel.com \
--cc=matan@nvidia.com \
--cc=michaelsh@marvell.com \
--cc=nicolas.chautru@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=ssahu@marvell.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).