DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ben Shelton <benjamin.h.shelton@intel.com>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Ben Shelton <benjamin.h.shelton@intel.com>
Subject: [dpdk-dev] [PATCH] ethdev: Add rte_tm_get_number_of_leaf_nodes to .map file
Date: Fri, 25 May 2018 14:59:43 -0500	[thread overview]
Message-ID: <20180525195943.16277-1-benjamin.h.shelton@intel.com> (raw)

The rte_tm_get_number_of_leaf_nodes() API function was added in DPDK
17.08.  However, it was added to the .map file with the wrong function
name (rte_tm_get_leaf_nodes), which was subsequently removed in commit
3e8ea3d ('lib: remove unused map symbols').

Add it back under the 17.08 release with the correct function name.

v2: Remove Gerrit Change-Id.

Signed-off-by: Ben Shelton <benjamin.h.shelton@intel.com>
---
 lib/librte_ethdev/rte_ethdev_version.map | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/librte_ethdev/rte_ethdev_version.map b/lib/librte_ethdev/rte_ethdev_version.map
index 9c9394c..c4251b6 100644
--- a/lib/librte_ethdev/rte_ethdev_version.map
+++ b/lib/librte_ethdev/rte_ethdev_version.map
@@ -148,6 +148,7 @@ DPDK_17.08 {
 	_rte_eth_dev_callback_process;
 	rte_eth_dev_adjust_nb_rx_tx_desc;
 	rte_tm_capabilities_get;
+	rte_tm_get_number_of_leaf_nodes;
 	rte_tm_hierarchy_commit;
 	rte_tm_level_capabilities_get;
 	rte_tm_mark_ip_dscp;
-- 
2.6.4

             reply	other threads:[~2018-05-25 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 19:59 Ben Shelton [this message]
2018-05-26 22:21 ` Ferruh Yigit
2018-05-26 22:23   ` Ferruh Yigit
  -- strict thread matches above, loose matches on Subject: below --
2018-05-25 19:56 Ben Shelton

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=20180525195943.16277-1-benjamin.h.shelton@intel.com \
    --to=benjamin.h.shelton@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --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).