From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 5A8241B465 for ; Wed, 28 Nov 2018 14:17:11 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7DA4731256DD; Wed, 28 Nov 2018 13:17:10 +0000 (UTC) Received: from [10.36.116.109] (ovpn-116-109.ams2.redhat.com [10.36.116.109]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 063952DE8A; Wed, 28 Nov 2018 13:17:06 +0000 (UTC) From: "Eelco Chaudron" To: "Thomas Monjalon" Cc: dev@dpdk.org, "David Marchand" , cristian.dumitrescu@intel.com Date: Wed, 28 Nov 2018 14:17:04 +0100 Message-ID: In-Reply-To: <34321981.0ZahcR99rh@xps> References: <154333204294.44971.12989297399338053044.stgit@dbuild> <3306361.jWiN20gDd9@xps> <34321981.0ZahcR99rh@xps> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Wed, 28 Nov 2018 13:17:10 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH 3/3] lib/librte_meter: update abi to include new rfc4115 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: , X-List-Received-Date: Wed, 28 Nov 2018 13:17:11 -0000 On 28 Nov 2018, at 13:51, Thomas Monjalon wrote: > 28/11/2018 13:40, Eelco Chaudron: >> >> On 28 Nov 2018, at 11:09, Thomas Monjalon wrote: >> >>> 28/11/2018 10:27, Eelco Chaudron: >>>> On 28 Nov 2018, at 9:38, David Marchand wrote: >>>>> On Tue, Nov 27, 2018 at 4:22 PM Eelco Chaudron >>>>> wrote: >>>>>> --- a/lib/librte_meter/Makefile >>>>>> +++ b/lib/librte_meter/Makefile >>>>>> -LIBABIVER := 2 >>>>>> +LIBABIVER := 3 >>>>> >>>>> As far as I understood the policy around the EXPERIMENTAL section, >>>>> you >>>>> don't need to bump the library version. >>>> >>>> Thought I would add the new function as none experimental, i.e. next >>>> version, but checkpatch did not allow me to do this. >>>> >>>> Tried to find info on what the right process was, as these functions >>>> are >>>> just another meter implementation using similar existing APIs. If >>>> anyone >>>> has any background on this please point me to it. >>> >>> It is documented here: >>> http://doc.dpdk.org/guides/contributing/versioning.html >>> >>> The case for "similar API" is not handled specifically so far. >>> So you need to introduce it as experimental. >> >> Thanks for the clarification, will update the APIs with >> __rte_experimental in the next iteration. > > You should also add this on top of the doxygen comment: > > * @warning > * @b EXPERIMENTAL: this API may change without prior notice Thanks, done!