diff mbox

[dpdk-dev] maintainers: fill git trees for net and crypto API

Message ID 20171106113651.10783-1-thomas@monjalon.net (mailing list archive)
State Accepted, archived
Headers

Checks

Context Check Description
ci/checkpatch warning coding style issues
ci/Intel-compilation success Compilation OK

Commit Message

Thomas Monjalon Nov. 6, 2017, 11:36 a.m. UTC 
  The ethdev API (including rte_flow) is managed in the dpdk-next-net tree.
The crypto and security API is managed in the dpdk-next-crypto tree.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---

Pablo, do you agree to manage rte_security patches in the crypto tree?

---
 MAINTAINERS | 4 ++++
 1 file changed, 4 insertions(+)

Comments

De Lara Guarch, Pablo Nov. 6, 2017, 4:38 p.m. UTC | #1 
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, November 6, 2017 11:37 AM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; De Lara Guarch, Pablo 
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] maintainers: fill git trees for net and 
> crypto API
> 
> The ethdev API (including rte_flow) is managed in the dpdk-next-net tree.
> The crypto and security API is managed in the dpdk-next-crypto tree.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> 
> Pablo, do you agree to manage rte_security patches in the crypto tree?

Hi Thomas,

I think it will depend on the amount of work that will be done in the
network drivers in the future. Can anyone working on the security
library say how much work is expected to be done there?

If there is not going to be huge work there, I don't mind
taking this in the subtree.

Thanks,
Pablo
Thomas Monjalon Nov. 12, 2017, 4:51 a.m. UTC | #2 
> > The ethdev API (including rte_flow) is managed in the dpdk-next-net tree.
> > The crypto and security API is managed in the dpdk-next-crypto tree.
> > 
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> > 
> > Pablo, do you agree to manage rte_security patches in the crypto tree?
> 
> Hi Thomas,
> 
> I think it will depend on the amount of work that will be done in the
> network drivers in the future. Can anyone working on the security
> library say how much work is expected to be done there?
> 
> If there is not going to be huge work there, I don't mind
> taking this in the subtree.

Applied without the rte_security one, as it is still a grey area.
diff mbox

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index 8ab08d2fc..c7c54f2d8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -246,11 +246,13 @@  F: test/test/test_mbuf.c
 
 Ethernet API
 M: Thomas Monjalon <thomas@monjalon.net>
+T: git://dpdk.org/next/dpdk-next-net
 F: lib/librte_ether/
 F: devtools/test-null.sh
 
 Flow API
 M: Adrien Mazarguil <adrien.mazarguil@6wind.com>
+T: git://dpdk.org/next/dpdk-next-net
 F: lib/librte_ether/rte_flow*
 
 Traffic Management API - EXPERIMENTAL
@@ -264,6 +266,7 @@  F: lib/librte_ether/rte_mtr*
 
 Crypto API
 M: Declan Doherty <declan.doherty@intel.com>
+T: git://dpdk.org/next/dpdk-next-crypto
 F: lib/librte_cryptodev/
 F: test/test/test_cryptodev*
 F: examples/l2fwd-crypto/
@@ -271,6 +274,7 @@  F: examples/l2fwd-crypto/
 Security API - EXPERIMENTAL
 M: Akhil Goyal <akhil.goyal@nxp.com>
 M: Declan Doherty <declan.doherty@intel.com>
+T: git://dpdk.org/next/dpdk-next-crypto
 F: lib/librte_security/
 F: doc/guides/prog_guide/rte_security.rst