From: Stephen Hemminger <stephen@networkplumber.org>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH] fib: promote experimental API's to stable
Date: Mon, 6 Sep 2021 17:34:27 -0700 [thread overview]
Message-ID: <20210906173427.3199543d@hermes.local> (raw)
In-Reply-To: <1630944075-363524-1-git-send-email-vladimir.medvedkin@intel.com>
On Mon, 6 Sep 2021 17:01:15 +0100
Vladimir Medvedkin <vladimir.medvedkin@intel.com> wrote:
> diff --git a/lib/fib/version.map b/lib/fib/version.map
> index be975ea..af76add 100644
> --- a/lib/fib/version.map
> +++ b/lib/fib/version.map
> @@ -1,4 +1,4 @@
> -EXPERIMENTAL {
> +DPDK_22 {
> global:
>
> rte_fib_add;
> --
I think you should add to existing version number
next prev parent reply other threads:[~2021-09-07 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 16:01 Vladimir Medvedkin
2021-09-07 0:34 ` Stephen Hemminger [this message]
2021-09-08 13:57 ` Medvedkin, Vladimir
2021-09-08 15:10 ` Stephen Hemminger
2021-09-08 17:02 ` Conor Walsh
2021-10-02 9:01 ` 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=20210906173427.3199543d@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).