From: Keith Wiles <keith.wiles@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 07/10] mlx5: update code to use __rte_weak macro
Date: Fri, 3 Aug 2018 09:06:02 -0500 [thread overview]
Message-ID: <20180803140605.43072-7-keith.wiles@intel.com> (raw)
In-Reply-To: <20180803140605.43072-1-keith.wiles@intel.com>
Signed-off-by: Keith Wiles <keith.wiles@intel.com>
---
drivers/net/mlx5/mlx5_rxtx.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/mlx5/mlx5_rxtx.c b/drivers/net/mlx5/mlx5_rxtx.c
index 2d14f8a6e..357c64838 100644
--- a/drivers/net/mlx5/mlx5_rxtx.c
+++ b/drivers/net/mlx5/mlx5_rxtx.c
@@ -2324,7 +2324,7 @@ removed_rx_burst(void *dpdk_txq __rte_unused,
* (e.g. mlx5_rxtx_vec_sse.c for x86).
*/
-uint16_t __attribute__((weak))
+__rte_weak uint16_t
mlx5_tx_burst_raw_vec(void *dpdk_txq __rte_unused,
struct rte_mbuf **pkts __rte_unused,
uint16_t pkts_n __rte_unused)
@@ -2332,7 +2332,7 @@ mlx5_tx_burst_raw_vec(void *dpdk_txq __rte_unused,
return 0;
}
-uint16_t __attribute__((weak))
+__rte_weak uint16_t
mlx5_tx_burst_vec(void *dpdk_txq __rte_unused,
struct rte_mbuf **pkts __rte_unused,
uint16_t pkts_n __rte_unused)
@@ -2340,7 +2340,7 @@ mlx5_tx_burst_vec(void *dpdk_txq __rte_unused,
return 0;
}
-uint16_t __attribute__((weak))
+__rte_weak uint16_t
mlx5_rx_burst_vec(void *dpdk_txq __rte_unused,
struct rte_mbuf **pkts __rte_unused,
uint16_t pkts_n __rte_unused)
@@ -2348,25 +2348,25 @@ mlx5_rx_burst_vec(void *dpdk_txq __rte_unused,
return 0;
}
-int __attribute__((weak))
+__rte_weak int
mlx5_check_raw_vec_tx_support(struct rte_eth_dev *dev __rte_unused)
{
return -ENOTSUP;
}
-int __attribute__((weak))
+__rte_weak int
mlx5_check_vec_tx_support(struct rte_eth_dev *dev __rte_unused)
{
return -ENOTSUP;
}
-int __attribute__((weak))
+__rte_weak int
mlx5_rxq_check_vec_support(struct mlx5_rxq_data *rxq __rte_unused)
{
return -ENOTSUP;
}
-int __attribute__((weak))
+__rte_weak int
mlx5_check_vec_rx_support(struct rte_eth_dev *dev __rte_unused)
{
return -ENOTSUP;
--
2.17.1
next prev parent reply other threads:[~2018-08-03 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 14:05 [dpdk-dev] [PATCH 01/10] eal: add shorthand " Keith Wiles
2018-08-03 14:05 ` [dpdk-dev] [PATCH 02/10] qat: update code to use " Keith Wiles
2018-08-29 9:27 ` Jozwiak, TomaszX
2018-08-03 14:05 ` [dpdk-dev] [PATCH 03/10] avf: " Keith Wiles
2018-08-03 14:05 ` [dpdk-dev] [PATCH 04/10] fm10k: " Keith Wiles
2018-08-03 14:06 ` [dpdk-dev] [PATCH 05/10] i40e: " Keith Wiles
2018-08-03 14:06 ` [dpdk-dev] [PATCH 06/10] ixgbe: " Keith Wiles
2018-08-03 14:06 ` Keith Wiles [this message]
2018-08-03 17:32 ` [dpdk-dev] [PATCH 07/10] mlx5: " Yongseok Koh
2018-08-03 14:06 ` [dpdk-dev] [PATCH 08/10] virtio: " Keith Wiles
2018-08-03 14:06 ` [dpdk-dev] [PATCH 09/10] acl: " Keith Wiles
2018-08-03 14:06 ` [dpdk-dev] [PATCH 10/10] bpf: " Keith Wiles
2018-10-03 16:09 ` [dpdk-dev] [PATCH 01/10] eal: add shorthand " Ferruh Yigit
2018-10-05 14:11 ` Wiles, Keith
2018-10-05 14:48 ` [dpdk-dev] [PATCH v2] add shorthand support for " Keith Wiles
2018-10-24 23:59 ` Thomas Monjalon
2018-10-05 14:49 ` [dpdk-dev] [PATCH 01/10] eal: add shorthand " Wiles, Keith
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=20180803140605.43072-7-keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@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).