From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id DE6351C6F1 for ; Fri, 13 Apr 2018 21:28:33 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Apr 2018 12:28:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,446,1517904000"; d="scan'208";a="216432091" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga005.jf.intel.com with ESMTP; 13 Apr 2018 12:28:29 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.176]) by IRSMSX104.ger.corp.intel.com ([169.254.5.171]) with mapi id 14.03.0319.002; Fri, 13 Apr 2018 20:28:28 +0100 From: "Mokhtar, Amr" To: "De Lara Guarch, Pablo" , "thomas@monjalon.net" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and security Thread-Index: AQHT0v+ZjzkgZXE6FkeAXL4W3wjBfKP/EyFw Date: Fri, 13 Apr 2018 19:28:27 +0000 Message-ID: <3D3765A8CDB52A4C8B410430AA19CB236ECA9F09@IRSMSX101.ger.corp.intel.com> References: <20180413081439.33050-1-pablo.de.lara.guarch@intel.com> In-Reply-To: <20180413081439.33050-1-pablo.de.lara.guarch@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjUwOTBiYmYtZjRjYS00NWI2LTgxMmUtZThhNTBlODI2MWYyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJmd3lMSWg4NnhuYXd5eGVjSFJiUEhqdkpUY1wvMkxnRE5KRXpFdDVoNlIybUdSRDFpU3dIN25HM1g1Z0NsVEc1NSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and security X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 19:28:34 -0000 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 su= btree 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 > > Subject: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and > security >=20 > Commits for bbdev and security libraries are merged > into the Next Crypto subtree. >=20 > Signed-off-by: Pablo de Lara > --- > MAINTAINERS | 2 ++ > 1 file changed, 2 insertions(+) >=20 > diff --git a/MAINTAINERS b/MAINTAINERS > index 77ceb63cb..c1892e490 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -312,6 +312,7 @@ F: lib/librte_ether/rte_mtr* >=20 > Baseband API - EXPERIMENTAL > M: Amr Mokhtar > +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 > M: Declan Doherty > +T: git://dpdk.org/next/dpdk-next-crypto > F: lib/librte_security/ > F: doc/guides/prog_guide/rte_security.rst >=20 > -- > 2.14.3