From: Thomas Monjalon <thomas@monjalon.net>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Ray Kinsella <mdr@ashroe.eu>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
Luca Boccassi <bluca@debian.org>,
Kevin Traynor <ktraynor@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: version rte_cryptodev_info_get function
Date: Mon, 20 Apr 2020 19:37:59 +0200 [thread overview]
Message-ID: <3812780.yFuDdFVEAc@thomas> (raw)
In-Reply-To: <2d0d9511-7e0c-4dc4-8a8e-f274ceb8a676@ashroe.eu>
20/04/2020 19:31, Ray Kinsella:
>
> Our only commitment is to the stability of the v19.11/v20 ABI, until v21.
>
> That said, once an ABI migrates from EXPERIMENTAL to v21, it _shouldn't_ be changing.
> We don't have a strict commitment to the v21 ABI until v20.11.
>
> However if v21 is changing across quarterlies (outside of additions) ... something else is wrong.
The only way to check a symbol is not changing in a quarterly release
is to test it. That's what we wanted to enforce:
compare 20.02 ABI in 20.05 release.
What other process do you suggest?
next prev parent reply other threads:[~2020-04-20 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 20:41 Arek Kusztal
2020-04-14 12:13 ` Akhil Goyal
2020-04-14 13:03 ` Thomas Monjalon
2020-04-14 13:52 ` Trahe, Fiona
2020-04-14 13:54 ` Ray Kinsella
2020-04-14 18:27 ` Trahe, Fiona
2020-04-15 17:24 ` Trahe, Fiona
2020-04-16 9:51 ` Bruce Richardson
2020-04-16 10:01 ` Thomas Monjalon
2020-04-17 7:24 ` Ray Kinsella
2020-04-17 9:31 ` Bruce Richardson
2020-04-17 9:42 ` Ray Kinsella
2020-04-17 10:17 ` Thomas Monjalon
2020-04-17 10:33 ` Ray Kinsella
2020-04-17 11:46 ` Trahe, Fiona
2020-04-17 16:01 ` Ray Kinsella
2020-04-20 16:59 ` Trahe, Fiona
2020-04-20 17:31 ` Ray Kinsella
2020-04-20 17:37 ` Thomas Monjalon [this message]
2020-04-21 6:01 ` Ray Kinsella
2020-04-21 9:36 ` Thomas Monjalon
2020-04-22 8:21 ` 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=3812780.yFuDdFVEAc@thomas \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=ktraynor@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.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).