From: Bruce Richardson <bruce.richardson@intel.com>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: <dev@dpdk.org>, <kamalakannan.r@intel.com>,
<yogesh.jangra@intel.com>, <harshad.suresh.narayane@intel.com>
Subject: Re: [PATCH V3] doc: announce the pipeline legacy API deprecation
Date: Fri, 10 Mar 2023 09:57:24 +0000 [thread overview]
Message-ID: <ZAr/BF2bzUi2hVYf@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230309200949.847639-1-cristian.dumitrescu@intel.com>
On Thu, Mar 09, 2023 at 08:09:49PM +0000, Cristian Dumitrescu wrote:
> 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.dumitrescu@intel.com>
Presumably the marking the new APIs as stable shouldn't need to be
"grandual", as we need stable replacements before deprecating any old
functions. However, since that seems to be covered here:
Acked-by: Bruce Richardson <bruce.richardson@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
>
next prev parent reply other threads:[~2023-03-10 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 19:54 [PATCH] doc: announce the legacy pipeline " Cristian Dumitrescu
2023-03-09 13:47 ` [PATCH V2] doc: announce the pipeline legacy " Cristian Dumitrescu
2023-03-09 20:09 ` [PATCH V3] " Cristian Dumitrescu
2023-03-10 6:02 ` Suresh Narayane, Harshad
2023-03-10 7:25 ` Jangra, Yogesh
2023-03-10 9:57 ` Bruce Richardson [this message]
2023-03-10 9:58 ` Nicolau, Radu
2023-03-10 12:19 ` R, Kamalakannan
2023-03-31 13:20 ` Thomas Monjalon
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=ZAr/BF2bzUi2hVYf@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=harshad.suresh.narayane@intel.com \
--cc=kamalakannan.r@intel.com \
--cc=yogesh.jangra@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).