From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 3/3] spp_vf: change inline func calls static inside
Date: Thu, 4 Apr 2019 18:57:40 +0900 [thread overview]
Message-ID: <1554371860-18206-4-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1554371860-18206-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Change `extern inline` funcitons to static to avoid compile error like
as following in some environments.
error: ‘rte_eth_tx_burst’ is static but used in inline function
‘spp_eth_tx_burst’ which is not static
In this case, static rte_eth_tx_burst() should not be called from inline
function.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
src/vf/common/spp_port.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/vf/common/spp_port.c b/src/vf/common/spp_port.c
index fd76d79..06422c3 100644
--- a/src/vf/common/spp_port.c
+++ b/src/vf/common/spp_port.c
@@ -57,7 +57,7 @@ spp_port_ability_init(void)
}
/* Get information of port ability. */
-extern inline void
+void
spp_port_ability_get_info(
int port_id, enum spp_port_rxtx rxtx,
struct spp_port_ability **info)
@@ -365,7 +365,7 @@ port_ability_each_operation(uint16_t port_id,
}
/* Wrapper function for rte_eth_rx_burst(). */
-extern inline uint16_t
+uint16_t
spp_eth_rx_burst(
uint16_t port_id, uint16_t queue_id __attribute__ ((unused)),
struct rte_mbuf **rx_pkts, const uint16_t nb_pkts)
@@ -387,7 +387,7 @@ spp_eth_rx_burst(
}
/* Wrapper function for rte_eth_tx_burst(). */
-extern inline uint16_t
+uint16_t
spp_eth_tx_burst(
uint16_t port_id, uint16_t queue_id __attribute__ ((unused)),
struct rte_mbuf **tx_pkts, uint16_t nb_pkts)
--
2.7.4
prev parent reply other threads:[~2019-04-04 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 9:57 [spp] [PATCH 0/3] Update for compile on CentOS7 ogawa.yasufumi
2019-04-04 9:57 ` [spp] [PATCH 1/3] spp_nfv: remove declaration in for loop ogawa.yasufumi
2019-04-04 9:57 ` [spp] [PATCH 2/3] spp_primary: " ogawa.yasufumi
2019-04-04 9:57 ` ogawa.yasufumi [this message]
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=1554371860-18206-4-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
/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).