From: "Mokhtar, Amr" <amr.mokhtar@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and security
Date: Fri, 13 Apr 2018 19:28:27 +0000 [thread overview]
Message-ID: <3D3765A8CDB52A4C8B410430AA19CB236ECA9F09@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20180413081439.33050-1-pablo.de.lara.guarch@intel.com>
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
next prev parent reply other threads:[~2018-04-13 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 8:14 Pablo de Lara
2018-04-13 19:28 ` Mokhtar, Amr [this message]
2018-04-19 13:13 ` De Lara Guarch, Pablo
2018-04-20 10:48 ` Mokhtar, Amr
2018-04-27 22:05 ` Thomas Monjalon
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=3D3765A8CDB52A4C8B410430AA19CB236ECA9F09@IRSMSX101.ger.corp.intel.com \
--to=amr.mokhtar@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).