From: David Marchand <david.marchand@redhat.com>
To: Ray Kinsella <mdr@ashroe.eu>,
Thomas Monjalon <thomas@monjalon.net>,
Neil Horman <nhorman@tuxdriver.com>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
dpdk stable <stable@dpdk.org>, dev <dev@dpdk.org>,
Eelco Chaudron <echaudro@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>,
Ian Stokes <ian.stokes@intel.com>,
Ilya Maximets <i.maximets@ovn.org>,
Luca Boccassi <bluca@debian.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] meter: move RFC4115 trTCM APIs as none experimental
Date: Thu, 16 Jan 2020 12:25:06 +0100 [thread overview]
Message-ID: <CAJFAV8wCYuDQEt3q_rDgzNO1h9ch9GSQRzn84QbTFSAddwzYjg@mail.gmail.com> (raw)
In-Reply-To: <20191217130742.165886.15691.stgit@netdev64>
On Tue, Dec 17, 2019 at 2:08 PM Eelco Chaudron <echaudro@redhat.com> wrote:
>
> Moved RFC4115 APIs to none experimental as they have been there
> since 19.02. Also, these APIs are the same as the none RFC4115 APIs.
>
> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
There is a discussion on the OVS ml at the moment to get these symbols
in the stable ABI for 19.11.
I want to understand how this would be done.
- I take this patch in 20.02, these symbols are added in the 20.0.1 ABI.
On the other hand, the 19.11 release maintains the 20.0 ABI.
Does it mean the backport adds these symbols with the 20.0 version in
the 19.11 branch?
Or is 20.0.1 version acceptable / a thing we want?
- These symbol already existed in the 20.0 ABI, versioned as EXPERIMENTAL.
We can go and remove these entries since we are not bound to preserve
the experimental APIs.
But, on the other hand, nothing should prevent us from keeping some
aliases so that the symbols versioned EXPERIMENTAL are still available
to existing users.
--
David Marchand
next prev parent reply other threads:[~2020-01-16 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:07 [dpdk-dev] [PATCH] meter: move RFC4115 trTCM APIs as none experimental Eelco Chaudron
2019-12-17 13:52 ` Dumitrescu, Cristian
2020-01-20 15:17 ` Thomas Monjalon
2020-01-16 11:25 ` David Marchand [this message]
2020-01-16 11:54 ` [dpdk-dev] [dpdk-stable] " Neil Horman
2020-01-16 12:42 ` Ferruh Yigit
2020-01-16 14:38 ` Thomas Monjalon
2020-01-17 8:27 ` David Marchand
2020-01-17 10:46 ` Luca Boccassi
2020-01-22 13:55 ` Ray Kinsella
2020-01-30 16:33 ` Ray Kinsella
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=CAJFAV8wCYuDQEt3q_rDgzNO1h9ch9GSQRzn84QbTFSAddwzYjg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=echaudro@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=i.maximets@ovn.org \
--cc=ian.stokes@intel.com \
--cc=ktraynor@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).