From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9B541A0561; Mon, 20 Apr 2020 19:38:03 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8145A1D44E; Mon, 20 Apr 2020 19:38:03 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 5DEC01C2C0 for ; Mon, 20 Apr 2020 19:38:02 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9F7B45C018F; Mon, 20 Apr 2020 13:38:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 20 Apr 2020 13:38:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= qs+Ij0RZMZIg9rWlIhL5S+Olo9PGB0kqX9V/pMpf030=; b=X7f6QHMztHUGLo42 4of9RYpmJ5iUyM0It7uwR4vz3+w4lc4HjAP5rw5AWgWN69Up8qP09nE8W04fr8FI LDWm3Oyt0VC3vJ/6A/nP1vXAJCri9VUmy+taOgNOQgALKe4SdOxtvpDzAhKOQemK cGlLL3avjNcz3+rzQ+cgdXeAeNxLrN1xlfCRhYSci8Z21M90JXwOf28N1MliASj5 pAyiYJFAwlab5oJckAT+e7Nt5dOilN+HOhvtwuyGF2IEFS+OYeiu4J7UyOwde1av DcKnng3MXkYlIB1O/VqjlrDDLoTC61LsfTlJU2yqSM2PjFIuwNkdQ41xVBPo+0vn i5Om0Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=qs+Ij0RZMZIg9rWlIhL5S+Olo9PGB0kqX9V/pMpf0 30=; b=QJDaeOcrlwCmHy5B1CiHHhtEYMefuiOhqboFKlo8x3yg6aMIjUgPsEE6S g1Y3Y93/IF9IcNu5koS+UjsZRd4ghlmYHIByT3g6iN6P8ri2OCI+ASjdA31HXklG f36yboM7yXEoCWbTrbPX7z/X4y0+W+fUCAmHv+01ylwTSTxJB0Rwx7jd6QgpQMXK mU+V2GIrwt49CG1QRY6LFePOTQ9m5VUpGfVvEfD4P35TBI2pbJpgAdkvCms3c2k7 SCSxj+MKsFQxKn8ohOOQixSmY5W/NOlC9GQ7+ckyUuw5N32DHxM11Y7QQmqhc3OJ x+bGH9IQJbVfjvoc+KogquRnnU0Nw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeefgdduuddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id F38DD3280059; Mon, 20 Apr 2020 13:37:59 -0400 (EDT) From: Thomas Monjalon To: "Trahe, Fiona" , "Richardson, Bruce" , Ray Kinsella Cc: "dev@dpdk.org" , "Kusztal, ArkadiuszX" , Neil Horman , Luca Boccassi , Kevin Traynor , "Yigit, Ferruh" , Akhil Goyal Date: Mon, 20 Apr 2020 19:37:59 +0200 Message-ID: <3812780.yFuDdFVEAc@thomas> In-Reply-To: <2d0d9511-7e0c-4dc4-8a8e-f274ceb8a676@ashroe.eu> References: <20200318204136.10508-1-arkadiuszx.kusztal@intel.com> <2d0d9511-7e0c-4dc4-8a8e-f274ceb8a676@ashroe.eu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] cryptodev: version rte_cryptodev_info_get function X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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?