DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Suresh Narayane, Harshad" <harshad.suresh.narayane@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"Nicolau, Radu" <radu.nicolau@intel.com>,
	"R, Kamalakannan" <kamalakannan.r@intel.com>
Subject: RE: [PATCH] doc: postpone deprecation of pipeline legacy API
Date: Thu, 20 Jul 2023 06:12:02 +0000	[thread overview]
Message-ID: <DM6PR11MB3242B9EE4E89725C19D68BD9AF3EA@DM6PR11MB3242.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230719151225.1658316-1-cristian.dumitrescu@intel.com>

-----Original Message-----
From: Dumitrescu, Cristian <cristian.dumitrescu@intel.com> 
Sent: Wednesday, July 19, 2023 8:42 PM
To: dev@dpdk.org
Cc: Richardson, Bruce <bruce.richardson@intel.com>; Nicolau, Radu <radu.nicolau@intel.com>; R, Kamalakannan <kamalakannan.r@intel.com>; Suresh Narayane, Harshad <harshad.suresh.narayane@intel.com>
Subject: [PATCH] doc: postpone deprecation of pipeline legacy API

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

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

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index fb771a0305..56ef906cdb 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -145,19 +145,16 @@ Deprecation Notices
   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.
+  will be deprecated and subsequently removed in DPDK 24.11 release.
+  Before this, the new pipeline library API (functions 
+ rte_swx_pipeline_*)  will gradually transition from experimental to stable status.
 
 * 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.
+  will be deprecated and subsequently removed in DPDK 24.11 release.
+  Before this, the new table library API (functions rte_swx_table_*)  
+ will gradually transition from experimental to stable status.
 
 * 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.
+  will be deprecated and subsequently removed in DPDK 24.11 release.
+  Before this, the new port library API (functions rte_swx_port_*)  
+ will gradually transition from experimental to stable status.
--
2.34.1

Acked-by: Harshad Narayane <harshad.suresh.narayane@intel.com>

  parent reply	other threads:[~2023-07-20  6:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 15:12 Cristian Dumitrescu
2023-07-19 16:08 ` Bruce Richardson
2023-07-20 10:37   ` Dumitrescu, Cristian
2023-07-28 16:02     ` Thomas Monjalon
2023-07-20  6:12 ` Suresh Narayane, Harshad [this message]
2023-07-20  8:18 ` Radu Nicolau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR11MB3242B9EE4E89725C19D68BD9AF3EA@DM6PR11MB3242.namprd11.prod.outlook.com \
    --to=harshad.suresh.narayane@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=kamalakannan.r@intel.com \
    --cc=radu.nicolau@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).