From: Jerin Jacob <jerinjacobk@gmail.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, "Kinsella, Ray" <ray.kinsella@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] rib: announce experimental tag removal of the rib API
Date: Sat, 7 Aug 2021 19:06:16 +0530 [thread overview]
Message-ID: <CALBAE1MDy8G3U+3YqPcZ4y_iLGY+4wX=-POjybJW7+8PtNXoHw@mail.gmail.com> (raw)
In-Reply-To: <1628162784-117829-1-git-send-email-vladimir.medvedkin@intel.com>
On Thu, Aug 5, 2021 at 4:56 PM Vladimir Medvedkin
<vladimir.medvedkin@intel.com> wrote:
>
> This patch announces the experimental tag removal of all rib APIs,
> which have been experimental for 2 years.
> API will be promoted to stable in DPDK 21.11
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index f4a4d00..afb599a 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -193,3 +193,5 @@ Deprecation Notices
> reserved bytes to 2 (from 3), and use 1 byte to indicate warnings and other
> information from the crypto/security operation. This field will be used to
> communicate events such as soft expiry with IPsec in lookaside mode.
> +
> +* rib: The ``rib`` library will be promoted from experimental to stable.
> --
> 2.7.4
>
next prev parent reply other threads:[~2021-08-07 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 11:26 Vladimir Medvedkin
2021-08-05 11:26 ` [dpdk-dev] [PATCH 2/2] fib: announce experimental tag removal of the fib API Vladimir Medvedkin
2021-08-05 13:52 ` Walsh, Conor
2021-08-07 13:35 ` Jerin Jacob
2021-08-07 13:36 ` Jerin Jacob [this message]
2021-10-02 8:59 ` [dpdk-dev] [PATCH 1/2] rib: announce experimental tag removal of the rib API David Marchand
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='CALBAE1MDy8G3U+3YqPcZ4y_iLGY+4wX=-POjybJW7+8PtNXoHw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ray.kinsella@intel.com \
--cc=vladimir.medvedkin@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).