DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Eelco Chaudron <echaudro@redhat.com>
Cc: dev@dpdk.org, David Marchand <david.marchand@redhat.com>,
	cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH 3/3] lib/librte_meter: update abi to include new rfc4115 function
Date: Wed, 28 Nov 2018 13:51:39 +0100	[thread overview]
Message-ID: <34321981.0ZahcR99rh@xps> (raw)
In-Reply-To: <F5B98C79-06B0-45C8-8440-82019AF1391C@redhat.com>

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 <echaudro@redhat.com>
> >>> 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                                         

  reply	other threads:[~2018-11-28 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 15:20 [dpdk-dev] [PATCH 0/3] lib/librte_meter: add RFC4115 trTCM meter support Eelco Chaudron
2018-11-27 15:21 ` [dpdk-dev] [PATCH 1/3] " Eelco Chaudron
2018-11-27 15:21 ` [dpdk-dev] [PATCH 2/3] test/test_meter: update meter test to include RFC4115 meters Eelco Chaudron
2018-11-27 15:21 ` [dpdk-dev] [PATCH 3/3] lib/librte_meter: update abi to include new rfc4115 function Eelco Chaudron
     [not found]   ` <CAJFAV8zUyBqEovvaChs3TO+Ah15T3davXPPkpDzzE2-fMQGD2g@mail.gmail.com>
2018-11-28  9:27     ` Eelco Chaudron
2018-11-28 10:09       ` Thomas Monjalon
2018-11-28 12:40         ` Eelco Chaudron
2018-11-28 12:51           ` Thomas Monjalon [this message]
2018-11-28 13:17             ` Eelco Chaudron

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=34321981.0ZahcR99rh@xps \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=echaudro@redhat.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).