Thanks & Regards,
Yogesh Jangra

-----Original Message-----
From: Dumitrescu, Cristian <cristian.dumitre...@intel.com> 
Sent: Friday, March 10, 2023 1:40 AM
To: dev@dpdk.org
Cc: R, Kamalakannan <kamalakanna...@intel.com>; Jangra, Yogesh 
<yogesh.jan...@intel.com>; Suresh Narayane, Harshad 
<harshad.suresh.naray...@intel.com>
Subject: [PATCH V3] doc: announce the pipeline legacy API deprecation

Announce the deprecation of the legacy pipeline, table and port library API and 
gradual stabilization of the new API.

Signed-off-by: Cristian Dumitrescu <cristian.dumitre...@intel.com>
---
 doc/guides/rel_notes/deprecation.rst | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst 
b/doc/guides/rel_notes/deprecation.rst
index 872847e938..66f2329b9c 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -135,3 +135,21 @@ Deprecation Notices
   Its removal has been postponed to let potential users report interest
   in maintaining it.
   In the absence of such interest, this library will be removed in DPDK 23.11.
+
+* pipeline: The pipeline library legacy API (functions rte_pipeline_*)
+  will be deprecated in DPDK 23.07 release and removed in DPDK 23.11
+  release. The new pipeline library API (functions rte_swx_pipeline_*)
+  will gradually transition from experimental to stable status
+  starting with DPDK 23.07 release.
+
+* table: The table library legacy API (functions rte_table_*) will be
+  deprecated in DPDK 23.07 release and removed in DPDK 23.11 release.
+  The new table library API (functions rte_swx_table_*) will gradually
+  transition from experimental to stable status starting with DPDK
+  23.07 release.
+
+* port: The port library legacy API (functions rte_port_*) will be
+  deprecated in DPDK 23.07 release and removed in DPDK 23.11 release.
+  The new port library API (functions rte_swx_port_*) will gradually
+  transition from experimental to stable status starting with DPDK
+  23.07 release.
--
2.34.1

Acked-by: Yogesh Jangra <yogesh.jan...@intel.com>

Reply via email to