DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v4] eventdev: add experimental tag back
Date: Wed, 01 May 2019 23:23:46 +0200	[thread overview]
Message-ID: <12997249.UctAg5hrmH@xps> (raw)
In-Reply-To: <7a91ba83-e614-89e5-5670-4d367e707314@redhat.com>

26/04/2019 19:18, Kevin Traynor:
> On 26/04/2019 17:33, Nikhil Rao wrote:
> > Add the experimental tag back to the Rx event adapter callback,
> > the Rx event callback register and the Rx event adapter statistics
> > retrieval functions due to an API change to be proposed in a
> > future patch.
> > 
> > This patch also adds the experimental tag to these
> > function definitions and adds the functions to the EXPERIMENTAL
> > section of the map file, these were missing previously.
> > 
> > Fixes: 80bdf91dc8ee ("eventdev: promote adapter functions as stable")
> > Cc: jerinj@marvell.com
> > 
> > Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> 
> Acked-by: Kevin Traynor <ktraynor@redhat.com>

Applied, thanks

  parent reply	other threads:[~2019-05-01 21:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23  5:50 [dpdk-dev] [PATCH] " Nikhil Rao
2019-04-23  5:50 ` Nikhil Rao
2019-04-23 10:58 ` Kevin Traynor
2019-04-23 10:58   ` Kevin Traynor
2019-04-24 17:34 ` [dpdk-dev] [PATCH v2] " Nikhil Rao
2019-04-24 17:34   ` Nikhil Rao
2019-04-25  5:42 ` [dpdk-dev] [PATCH v3] " Nikhil Rao
2019-04-25  5:42   ` Nikhil Rao
2019-04-25  9:55   ` Kevin Traynor
2019-04-25  9:55     ` Kevin Traynor
2019-04-26 16:33 ` [dpdk-dev] [PATCH v4] " Nikhil Rao
2019-04-26 16:33   ` Nikhil Rao
2019-04-26 17:18   ` Kevin Traynor
2019-04-26 17:18     ` Kevin Traynor
2019-05-01 21:23     ` Thomas Monjalon [this message]
2019-05-01 21:23       ` Thomas Monjalon
2019-04-28 17:05 Jerin Jacob Kollanukkaran
2019-04-28 17:05 ` Jerin Jacob Kollanukkaran

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=12997249.UctAg5hrmH@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ktraynor@redhat.com \
    --cc=nikhil.rao@intel.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).