From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 72FAAA0487 for ; Mon, 29 Jul 2019 18:34:14 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4F3A01BF10; Mon, 29 Jul 2019 18:34:13 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 68BBE1BF04 for ; Mon, 29 Jul 2019 18:34:11 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E6544223CF; Mon, 29 Jul 2019 12:34:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 29 Jul 2019 12:34:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=8fy+K5KxVjtBchEYDg77/SB/Sp/U1ode1GQXRV/NXew=; b=BK9LwYhQIplV 9qjBcsYqGafaZV6hGCJH8gpYeDHujUeuc9NFZvb7iyXM8UrN/HEcTGJEn/H3uwQR CY+37qUehp9qY7cWdroJyl3zCCG6i9wSbDPTAvMJehtasvkCD7fx5ihehsZshTPt pd+qMDmLLPRusqqQY3RpcEsVZWCSTmI= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=8fy+K5KxVjtBchEYDg77/SB/Sp/U1ode1GQXRV/NX ew=; b=BH0msMyIHeJiL6leFrT7aYaaHfxf8qXUIW7X++ZQFnwt6NyhWZTAZDGPQ /pYyDzQiwgKrQFUNCRdnClgI7/isdq7nBc9H+nK3u9kP9kTdu3PhSPAcumpdFB16 Sisvz5nfk3N2OAHRYo2t0BJwbTi37VDLnpD0zP2XQv1mQYd9yDwaWuMFao8TdOLi HlzK9iHVR7YFp6hq9mbvukVgepayuaT2+JwFDMz8e5P3kNaftfnrgRxzvz1k/z2o mIqMrUMzfqKtM/7ghtvAYriqWLPK6YOgfS/2d/fpBvFLvAjtVAscEVCJX4LVZGwA Asyaa7AKrVUDb8oKGXCFfCbarjlKQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrledugddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (unknown [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 6DD8A380075; Mon, 29 Jul 2019 12:34:07 -0400 (EDT) From: Thomas Monjalon To: Bernard Iremonger Cc: dev@dpdk.org, Akhil Goyal , Anoob Joseph , "konstantin.ananyev@intel.com" , Jerin Jacob Kollanukkaran , Narayana Prasad Raju Athreya Date: Mon, 29 Jul 2019 18:33:36 +0200 Message-ID: <3165113.5OK8ffLHOj@xps> In-Reply-To: References: <1562835937-24141-1-git-send-email-bernard.iremonger@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [EXT] [PATCH] doc: deprecate legacy code path in ipsec-secgw 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > > > All the functionality of the legacy code path in now available in the librte_ipsec > > > library. It is planned to deprecate the legacy code path in the 19.11 release and > > > remove the legacy code path in the 20.02 release. > > > > > > Signed-off-by: Bernard Iremonger > > > Acked-by: Konstantin Ananyev > > > Acked-by: Fan Zhang > > > Acked-by: Akhil Goyal > > > --- > > > doc/guides/rel_notes/deprecation.rst | 5 +++++ > > > 1 file changed, 5 insertions(+) > > > > > Acked-by: Anoob Joseph > > Applied to dpdk-next-crypto Why do we have a deprecation notice for some code path in an example? The deprecation notices are for the API. I think you can drop the legacy code in 19.11, and I don't merge this patch in master.