From: Nikhil Rao <nikhil.rao@intel.com>
To: jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] eventdev: add API to map file
Date: Tue, 17 Oct 2017 23:17:45 +0530 [thread overview]
Message-ID: <1508262465-16214-1-git-send-email-nikhil.rao@intel.com> (raw)
In-Reply-To: <1508182646-12184-1-git-send-email-nikhil.rao@intel.com>
Add rte_event_eth_rx_adapter_service_id_get to map file. Also order
function names alphabetically.
Fixes: 9c38b704d280 ("eventdev: add eth Rx adapter implementation")
Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
---
v2:
* Re-insert newline after function name list
* Order function names alphabetically
lib/librte_eventdev/rte_eventdev_version.map | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/librte_eventdev/rte_eventdev_version.map b/lib/librte_eventdev/rte_eventdev_version.map
index 828b9a340..800ca6e92 100644
--- a/lib/librte_eventdev/rte_eventdev_version.map
+++ b/lib/librte_eventdev/rte_eventdev_version.map
@@ -60,9 +60,10 @@ DPDK_17.11 {
rte_event_eth_rx_adapter_free;
rte_event_eth_rx_adapter_queue_add;
rte_event_eth_rx_adapter_queue_del;
+ rte_event_eth_rx_adapter_service_id_get;
rte_event_eth_rx_adapter_start;
- 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_stop;
} DPDK_17.08;
--
2.14.1.145.gb3622a4
next prev parent reply other threads:[~2017-10-17 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 19:37 [dpdk-dev] [PATCH] " Nikhil Rao
2017-10-16 11:12 ` De Lara Guarch, Pablo
2017-10-16 11:40 ` Pavan Nikhilesh Bhagavatula
2017-10-17 17:47 ` Nikhil Rao [this message]
2017-10-18 3:49 ` [dpdk-dev] [PATCH v2] " 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=1508262465-16214-1-git-send-email-nikhil.rao@intel.com \
--to=nikhil.rao@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).