From: "Kinsella, Ray" <mdr@ashroe.eu>
To: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Neil Horman <nhorman@tuxdriver.com>,
David Marchand <david.marchand@redhat.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Arek Kusztal <arkadiuszx.kusztal@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Ori Kam <orika@mellanox.com>
Subject: Re: [dpdk-dev] Please note: v21 ABI notification
Date: Fri, 14 Aug 2020 16:23:38 +0100 [thread overview]
Message-ID: <0efd32f4-dd9c-0b38-5fba-59ed85ec1a4d@ashroe.eu> (raw)
In-Reply-To: <244780af-5d71-44db-38b0-e7948782aed5@ashroe.eu>
Hi folks,
Now is the time to remove old ABI compatibility preserving code.
Remove versioning code:
* Cryptodev
Fiona Trahe <fiona.trahe@intel.com>
Arek Kusztal <arkadiuszx.kusztal@intel.com>
* Mempool
Olivier Matz <olivier.matz@6wind.com>
Remove alias to experimental:
* Metering
Ferruh Yigit <ferruh.yigit@intel.com>
Finally,
Along the way I noted the following public symbols that are not assigned to a version node.
* Regex Device
Ori Kam <orika@mellanox.com>
Symbols: -
rte_regexdev_unregister
rte_regexdev_register
rte_regexdev_get_device_by_name
rte_regexdev_is_valid_dev
Thanks,
Ray Kinsella
On 14/08/2020 16:16, Kinsella, Ray wrote:
> Please note,
>
> ABI v21 has been declared aligned with the DPDK 20.11 release.
> (https://git.dpdk.org/dpdk/commit/?id=4f86c0ba19ba065c8c32a5b0111efc7bb74c9b96)
>
> The requirement to preserve compatibility with the previous major ABI version v20
> in DPDK 19.11 is now dropped. This is commonly known as the ABI breakage window,
> and some amended rules apply for the duration of this cycle:
>
> * The requirement to preserve compatibility with the previous major ABI
> version v20, no longer applies.
>
> * Contributors of compatibility preserving code and/or symbol aliases to
> experimental in previous releases, are now kindly asked to remove this code.
>
> I will send a direct notification to this group as a followup to this mail.
>
> * Symbol versioning references to the old ABI version v20, have been
> updated to reference the new ABI version v21.
>
> * Finally, please note, the ABI breakage window is *not* permission to
> circumvent the other aspects of the procedures to make ABI changes,
> that is, 3 ACKs of the requirement to break the ABI and
> the observance of a deprecation notice are still considered mandatory.
>
> Kinds regards,
>
> Ray Kinsella
> ABI Maintainer
>
prev parent reply other threads:[~2020-08-14 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 15:16 Kinsella, Ray
2020-08-14 15:23 ` Kinsella, Ray [this message]
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=0efd32f4-dd9c-0b38-5fba-59ed85ec1a4d@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=arkadiuszx.kusztal@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=orika@mellanox.com \
--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).