From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3B83820A96; Sun, 12 Nov 2017 01:58:48 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 12 Nov 2017 01:58:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=wSwFgC+w5cnHEUCKqu3ZWJkmCS huOmNzYwog1Permq8=; b=NHD14uiZyjXurVmkTTIkqcTCLL/+N8BcDWPOIAW6ds 0KyIlVMrMZO+Qn/JussEZllTo++aGzWp8nRRdk51FLxbE7kILrxz7gEj5/3FIaNx ED1S3Am+soso6veJ84IqkW2YFzsHlfaShPhMYhiOzQTxCy2ZBlIIqkZscORUE/I8 A= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=wSwFgC +w5cnHEUCKqu3ZWJkmCShuOmNzYwog1Permq8=; b=RHn4OQhnyHhCoH3vHs0+J0 UlvIuf8w9lT9NJnIzrTL7dJky6MZGwXqX8TdduOYL1BZNMNlLa0mTBg2ecwTOttY cgjVh8iam/frq5cQRQUhHsRIqqyidtzAFau/CfJaE6UP7hinBY5yOCLrB2IL+DK1 CUOjAleGGkz+ho9K0Evn0tfZcJoo6AXdaTPROjQGZjMVIsFCcggFnKntiFqvLWuI guYjixO/OW3+S+X6ZVH98T5oRmD8pAzqCkUGcMLHFZbN7ws+d/WjXtiLE12ohuQc OlkUQ0RaA2HIAWhEwMgCHc8oEbGoLg1h19I/RIQqavnKvPXAgxf8v1LpWuSl1D3Q == X-ME-Sender: Received: from xps.localnet (unknown [12.232.154.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 0405C7E1DB; Sun, 12 Nov 2017 01:58:48 -0500 (EST) From: Thomas Monjalon To: Pablo de Lara , ferruh.yigit@intel.com Cc: dev@dpdk.org Date: Sun, 12 Nov 2017 05:51:28 +0100 Message-ID: <1746970.1JDTCvcneo@xps> In-Reply-To: <20171106163822.2849-1-pablo.de.lara.guarch@intel.com> References: <20171106113651.10783-1-thomas@monjalon.net> <20171106163822.2849-1-pablo.de.lara.guarch@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] maintainers: fill git trees for net and crypto API 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: Sun, 12 Nov 2017 06:58:49 -0000 > > 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.