[PATCH] maintainers: call out subtree for bbdev and security

[PATCH] maintainers: call out subtree for bbdev and security

[Pablo de Lara]

Commits for bbdev and security libraries are merged
into the Next Crypto subtree.

Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 77ceb63cb..c1892e490 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -312,6 +312,7 @@ F: lib/librte_ether/rte_mtr*
 
 Baseband API - EXPERIMENTAL
 M: Amr Mokhtar <amr.mokhtar@intel.com>
+T: git://dpdk.org/next/dpdk-next-crypto
 F: lib/librte_bbdev/
 F: doc/guides/prog_guide/bbdev.rst
 F: drivers/baseband/
@@ -332,6 +333,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
 
-- 
2.14.3

Re: [PATCH] maintainers: call out subtree for bbdev and security

[Mokhtar, Amr]

Hi Pablo, Thomas,
There are some update patches undergoing submission for bbdev on master.
Do we need to copy them over from master to next-crypto-subtree?
And how this will work in the future? Will all future patches go to next subtree and back to master?

Best regards,
Amr

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Friday 13 April 2018 09:15
> To: thomas@monjalon.net
> Cc: dev@dpdk.org; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and
> security
> 
> Commits for bbdev and security libraries are merged
> into the Next Crypto subtree.
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 77ceb63cb..c1892e490 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -312,6 +312,7 @@ F: lib/librte_ether/rte_mtr*
> 
>  Baseband API - EXPERIMENTAL
>  M: Amr Mokhtar <amr.mokhtar@intel.com>
> +T: git://dpdk.org/next/dpdk-next-crypto
>  F: lib/librte_bbdev/
>  F: doc/guides/prog_guide/bbdev.rst
>  F: drivers/baseband/
> @@ -332,6 +333,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
> 
> --
> 2.14.3

Re: [PATCH] maintainers: call out subtree for bbdev and security

[De Lara Guarch, Pablo]

Hi Amr,

> -----Original Message-----
> From: Mokhtar, Amr
> Sent: Friday, April 13, 2018 8:28 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> thomas@monjalon.net
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and
> security
> 
> Hi Pablo, Thomas,
> There are some update patches undergoing submission for bbdev on master.
> Do we need to copy them over from master to next-crypto-subtree?
> And how this will work in the future? Will all future patches go to next subtree
> and back to master?

Sorry for not replying to this earlier. These patches will get merged in next-crypto subtree
and then, after a pull request, Thomas will merge the changes into mainline.

Pablo

Re: [PATCH] maintainers: call out subtree for bbdev and security

[Mokhtar, Amr]

> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday 19 April 2018 14:14
> To: Mokhtar, Amr <amr.mokhtar@intel.com>; thomas@monjalon.net
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and
> security
> 
> Hi Amr,
> 
> > -----Original Message-----
> > From: Mokhtar, Amr
> > Sent: Friday, April 13, 2018 8:28 PM
> > To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> > thomas@monjalon.net
> > Cc: dev@dpdk.org
> > Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev
> and
> > security
> >
> > Hi Pablo, Thomas,
> > There are some update patches undergoing submission for bbdev on
> master.
> > Do we need to copy them over from master to next-crypto-subtree?
> > And how this will work in the future? Will all future patches go to next
> subtree
> > and back to master?
> 
> Sorry for not replying to this earlier. These patches will get merged in next-
> crypto subtree
> and then, after a pull request, Thomas will merge the changes into mainline.
> 
> Pablo

Sounds great. Thanks Pablo.

Re: [PATCH] maintainers: call out subtree for bbdev and security

[Thomas Monjalon]

13/04/2018 10:14, Pablo de Lara:
> Commits for bbdev and security libraries are merged
> into the Next Crypto subtree.
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

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

Applied, thanks