From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Nikhil Rao <nikhil.rao@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] eventdev: add experimental tag back
Date: Sun, 28 Apr 2019 17:05:35 +0000 [thread overview]
Message-ID: <BYAPR18MB2424E39C3DD7C27EE7B6BD21C8380@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
Message-ID: <20190428170535.U5gcjEJ2vlbuLwBlH0CmAd_2yZ7M1jLqfFsMR-bZdeY@z> (raw)
> -----Original Message-----
> From: Nikhil Rao <nikhil.rao@intel.com>
> Sent: Friday, April 26, 2019 10:04 PM
> To: thomas@monjalon.net
> Cc: dev@dpdk.org; Nikhil Rao <nikhil.rao@intel.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>
> Subject: [EXT] [PATCH v4] eventdev: add experimental tag back
> 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: Jerin Jacob <jerinj@marvell.com>
next reply other threads:[~2019-04-28 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 17:05 Jerin Jacob Kollanukkaran [this message]
2019-04-28 17:05 ` Jerin Jacob Kollanukkaran
-- strict thread matches above, loose matches on Subject: below --
2019-04-23 5:50 [dpdk-dev] [PATCH] " Nikhil Rao
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
2019-05-01 21:23 ` Thomas Monjalon
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=BYAPR18MB2424E39C3DD7C27EE7B6BD21C8380@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.com \
--cc=thomas@monjalon.net \
/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).