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 8DED0A0487 for ; Mon, 29 Jul 2019 22:07:09 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5FFED1BF65; Mon, 29 Jul 2019 22:07:09 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id F33251BF23 for ; Mon, 29 Jul 2019 22:07:06 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jul 2019 13:07:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,324,1559545200"; d="scan'208";a="371223441" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga006.fm.intel.com with ESMTP; 29 Jul 2019 13:07:04 -0700 Received: from irsmsx155.ger.corp.intel.com (163.33.192.3) by IRSMSX153.ger.corp.intel.com (163.33.192.75) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 29 Jul 2019 21:07:03 +0100 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.164]) by irsmsx155.ger.corp.intel.com ([169.254.14.201]) with mapi id 14.03.0439.000; Mon, 29 Jul 2019 21:07:03 +0100 From: "Ananyev, Konstantin" To: Thomas Monjalon , "Iremonger, Bernard" CC: "dev@dpdk.org" , Akhil Goyal , "Anoob Joseph" , Jerin Jacob Kollanukkaran , Narayana Prasad Raju Athreya Thread-Topic: [dpdk-dev] [EXT] [PATCH] doc: deprecate legacy code path in ipsec-secgw Thread-Index: AQHVRiuUahjna7FP7EWKTttMwp/2XKbiBc/g Date: Mon, 29 Jul 2019 20:07:02 +0000 Message-ID: <2601191342CEEE43887BDE71AB9772580168A5EF51@irsmsx105.ger.corp.intel.com> References: <1562835937-24141-1-git-send-email-bernard.iremonger@intel.com> <3165113.5OK8ffLHOj@xps> In-Reply-To: <3165113.5OK8ffLHOj@xps> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYWFlZDY2NzgtZTQ0Ny00MzU4LTk5ZTQtNTdmNGYzOGVlYTY1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTFVKa1EycTJwSUVXV0lraDF5czVibTk3OENYMXhCSnRSQ0x1WGl4aW5xTm1yeEJzRGZyd1NcLzIzTHl6eTNDWTMifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.2.0.6 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] [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" > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Monday, July 29, 2019 5:34 PM > To: Iremonger, Bernard > Cc: dev@dpdk.org; Akhil Goyal ; Anoob Joseph ; Ananyev, Konstantin > ; Jerin Jacob Kollanukkaran ; Narayana Prasad Raju Athreya > > Subject: Re: [dpdk-dev] [EXT] [PATCH] doc: deprecate legacy code path in = ipsec-secgw >=20 > > > > All the functionality of the legacy code path in now available in t= he 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 >=20 > Why do we have a deprecation notice for some code path in an example? > The deprecation notices are for the API. >=20 > I think you can drop the legacy code in 19.11, > and I don't merge this patch in master. Ok, if we don't need a formal deprecation note for that - even better. Thanks Konstantin