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 3DB65A0588; Thu, 16 Apr 2020 12:01:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0AC311DBBA; Thu, 16 Apr 2020 12:01:07 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id CDCCD1D9D1 for ; Thu, 16 Apr 2020 12:01:05 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 6C921751; Thu, 16 Apr 2020 06:01:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 16 Apr 2020 06:01:04 -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=mesmtp; bh=g88SHMWxZUB7sLPsdjojue3/yS/0UXWcHq45M5qy1O8=; b=Xx2oMFxwjxSd sFiVhvgPtnpkzzV47i8IU9NvvTIVlNi59qmEyVNvr1QAJTmZyjmU5SaFl7MgBv3G +WFX6ZMsvaS5IBtxm9FOiNaZBaqbEWjcT/m3DXO3RzhR16JtoDWQyAGpHUUV0ynm +Jf2Z0uGuRAYPvffxumszErWeVTqJYI= 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=g88SHMWxZUB7sLPsdjojue3/yS/0UXWcHq45M5qy1 O8=; b=jgXJDlvDFVBBVQkzgScPunCZQF7FA23VRL2ms2h0emCD0t79A2cVZYcY2 HnHi7scyVDgixLAwR33pjdh4xmenjgn2tPT9uS25IQ+L1XPje4y2W20sEgexEYbO ogBVrNlbzQdxmnaE+tMH3DWfVr5qx5AmZNRFn9tbeO+soE0BHJ4A3xMVfi4pqD9M wqF0MRBkoMeigwYMZPjvsdgrgI7vcN2KYlZseYqxHZYh1ULZQJ1IrWhZfU+K2akW 9m7vBQ7cjTQ4ZOWY2wVThj2la9Rdbc4j1VxKjT+IKy7Ayqz1mKjVpAXYXuXx4bPD b2EdIDG53QlLaBFgwFnbnBU3F5kOA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrfeehgddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 B3E223280066; Thu, 16 Apr 2020 06:01:02 -0400 (EDT) From: Thomas Monjalon To: "Trahe, Fiona" , Bruce Richardson Cc: Ray Kinsella , "dev@dpdk.org" , "Kusztal, ArkadiuszX" Date: Thu, 16 Apr 2020 12:01:01 +0200 Message-ID: <4271918.xgJ6IN8ObU@thomas> In-Reply-To: <20200416095124.GA1691@bricha3-MOBL.ger.corp.intel.com> References: <20200318204136.10508-1-arkadiuszx.kusztal@intel.com> <20200416095124.GA1691@bricha3-MOBL.ger.corp.intel.com> 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" 16/04/2020 11:51, Bruce Richardson: > On Wed, Apr 15, 2020 at 06:24:19PM +0100, Trahe, Fiona wrote: > > 5a. If in 20.05 we add a version of a fn which breaks ABI 20.0, what should the name of the original function be? fn_v20, or fn_v20.0 > > In technical terms it really doesn't matter, it's just a name that will be > looked up in a table. I don't think we strictly enforce the naming, so > whatever is clearest is best. I'd suggest the former. Each release can have a new ABI. The same function can have a different version in 20.02, 20.05 and 20.08. If you name it fn_v20 in 20.05, what will be the name for the new version in 20.08? I suggest using the release number when versioning a function.