From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Rao, Nikhil" <nikhil.rao@intel.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eventdev: add API to map file
Date: Mon, 16 Oct 2017 11:12:02 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC347BD@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1508182646-12184-1-git-send-email-nikhil.rao@intel.com>
Hi Nikhil,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nikhil Rao
> Sent: Monday, October 16, 2017 8:37 PM
> To: jerin.jacob@caviumnetworks.com
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] eventdev: add API to map file
>
> Add rte_event_eth_rx_adapter_service_id_get to map file
>
> Fixes: 9c38b704d280 ("eventdev: add eth Rx adapter implementation")
>
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> ---
> lib/librte_eventdev/rte_eventdev_version.map | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_eventdev/rte_eventdev_version.map
> b/lib/librte_eventdev/rte_eventdev_version.map
> index 828b9a3..8ce2641 100644
> --- a/lib/librte_eventdev/rte_eventdev_version.map
> +++ b/lib/librte_eventdev/rte_eventdev_version.map
> @@ -64,5 +64,5 @@ DPDK_17.11 {
> rte_event_eth_rx_adapter_stop;
> rte_event_eth_rx_adapter_stats_get;
> rte_event_eth_rx_adapter_stats_reset;
> -
> + rte_event_eth_rx_adapter_service_id_get;
Do not remove the blank line after the functions.
Also, the functions should be listed in alphabetical order.
Thanks,
Pablo
next prev parent reply other threads:[~2017-10-16 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 19:37 Nikhil Rao
2017-10-16 11:12 ` De Lara Guarch, Pablo [this message]
2017-10-16 11:40 ` Pavan Nikhilesh Bhagavatula
2017-10-17 17:47 ` [dpdk-dev] [PATCH v2] " Nikhil Rao
2017-10-18 3:49 ` Jerin Jacob
2017-10-18 9:21 ` [dpdk-dev] [PATCH] doc: add event eth Rx adapter library Nikhil Rao
2017-10-21 15:59 ` Jerin Jacob
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=E115CCD9D858EF4F90C690B0DCB4D8976CC347BD@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).