From: "Carrillo, Erik G" <erik.g.carrillo@intel.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>
Cc: "pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"Ma, Liang J" <liang.j.ma@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eventdev: promote adapter functions as stable
Date: Thu, 18 Apr 2019 21:47:00 +0000 [thread overview]
Message-ID: <BE54F058557D9A4FAC1D84E2FC6D8757233FAD1F@fmsmsx115.amr.corp.intel.com> (raw)
In-Reply-To: <20190418120538.16020-1-jerinj@marvell.com>
> -----Original Message-----
> From: jerinj@marvell.com [mailto:jerinj@marvell.com]
> Sent: Thursday, April 18, 2019 7:06 AM
> To: dev@dpdk.org; Thomas Monjalon <thomas@monjalon.net>; Jerin Jacob
> <jerinj@marvell.com>; Mattias Rönnblom
> <mattias.ronnblom@ericsson.com>; Van Haaren, Harry
> <harry.van.haaren@intel.com>; Gujjar, Abhinandan S
> <abhinandan.gujjar@intel.com>; Rao, Nikhil <nikhil.rao@intel.com>; Carrillo,
> Erik G <erik.g.carrillo@intel.com>
> Cc: pbhagavatula@marvell.com; hemant.agrawal@nxp.com;
> nipun.gupta@nxp.com; Ma, Liang J <liang.j.ma@intel.com>
> Subject: [dpdk-dev] [PATCH] eventdev: promote adapter functions as stable
>
> From: Jerin Jacob <jerinj@marvell.com>
>
> Promote the adapter functions and rte_event_port_unlinks_in_progress()
> as stable as it's been added for a while now and multiple drivers and test
> application like test-eventdev has been tested using the adapter APIs.
>
> Cc: nikhil.rao@intel.com
> Cc: erik.g.carrillo@intel.com
> Cc: abhinandan.gujjar@intel.com
> Cc: pbhagavatula@marvell.com
> Cc: hemant.agrawal@nxp.com
> Cc: nipun.gupta@nxp.com
> Cc: harry.van.haaren@intel.com
> Cc: mattias.ronnblom@ericsson.com
> Cc: liang.j.ma@intel.com
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
Hi Jerin,
The "__rte_experimental" tag was removed from function prototypes in header files while still leaving the following text in the Doxygen comments:
* @warning
* @b EXPERIMENTAL: this API may change without prior notice
Regards,
Erik
next prev parent reply other threads:[~2019-04-18 21:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 12:05 jerinj
2019-04-18 12:05 ` jerinj
2019-04-18 21:47 ` Carrillo, Erik G [this message]
2019-04-18 21:47 ` Carrillo, Erik G
2019-04-19 10:53 ` Jerin Jacob Kollanukkaran
2019-04-19 10:53 ` Jerin Jacob Kollanukkaran
2019-04-19 12:10 ` [dpdk-dev] [PATCH v2] " jerinj
2019-04-19 12:10 ` jerinj
2019-04-21 12:44 ` Gujjar, Abhinandan S
2019-04-21 12:44 ` Gujjar, Abhinandan S
2019-04-22 11:15 ` Thomas Monjalon
2019-04-22 11:15 ` Thomas Monjalon
2019-04-22 11:32 ` Rao, Nikhil
2019-04-22 11:32 ` Rao, Nikhil
2019-04-22 12:48 ` Thomas Monjalon
2019-04-22 12:48 ` 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=BE54F058557D9A4FAC1D84E2FC6D8757233FAD1F@fmsmsx115.amr.corp.intel.com \
--to=erik.g.carrillo@intel.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=liang.j.ma@intel.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=nikhil.rao@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@marvell.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).