From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] maintainers: fill git trees for net and crypto API Date: Sun, 12 Nov 2017 05:51:28 +0100 Message-ID: <1746970.1JDTCvcneo@xps> References: <20171106113651.10783-1-thomas@monjalon.net> <20171106163822.2849-1-pablo.de.lara.guarch@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Pablo de Lara , ferruh.yigit@intel.com Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 8819E1B258 for ; Sun, 12 Nov 2017 07:58:48 +0100 (CET) In-Reply-To: <20171106163822.2849-1-pablo.de.lara.guarch@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > > 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 > > --- > > > > 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.