DPDK patches and discussions
 help / color / mirror / Atom feed
From: Keith Wiles <keith.wiles@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 04/10] fm10k: update code to use __rte_weak macro
Date: Fri,  3 Aug 2018 09:05:59 -0500	[thread overview]
Message-ID: <20180803140605.43072-4-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/fm10k/fm10k_ethdev.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/net/fm10k/fm10k_ethdev.c b/drivers/net/fm10k/fm10k_ethdev.c
index 541a49b75..e43b16d4e 100644
--- a/drivers/net/fm10k/fm10k_ethdev.c
+++ b/drivers/net/fm10k/fm10k_ethdev.c
@@ -129,13 +129,13 @@ fm10k_mbx_unlock(struct fm10k_hw *hw)
 }
 
 /* Stubs needed for linkage when vPMD is disabled */
-int __attribute__((weak))
+__rte_weak int
 fm10k_rx_vec_condition_check(__rte_unused struct rte_eth_dev *dev)
 {
 	return -1;
 }
 
-uint16_t __attribute__((weak))
+__rte_weak uint16_t
 fm10k_recv_pkts_vec(
 	__rte_unused void *rx_queue,
 	__rte_unused struct rte_mbuf **rx_pkts,
@@ -144,7 +144,7 @@ fm10k_recv_pkts_vec(
 	return 0;
 }
 
-uint16_t __attribute__((weak))
+__rte_weak uint16_t
 fm10k_recv_scattered_pkts_vec(
 		__rte_unused void *rx_queue,
 		__rte_unused struct rte_mbuf **rx_pkts,
@@ -153,33 +153,33 @@ fm10k_recv_scattered_pkts_vec(
 	return 0;
 }
 
-int __attribute__((weak))
+__rte_weak int
 fm10k_rxq_vec_setup(__rte_unused struct fm10k_rx_queue *rxq)
 
 {
 	return -1;
 }
 
-void __attribute__((weak))
+__rte_weak void
 fm10k_rx_queue_release_mbufs_vec(
 		__rte_unused struct fm10k_rx_queue *rxq)
 {
 	return;
 }
 
-void __attribute__((weak))
+__rte_weak void
 fm10k_txq_vec_setup(__rte_unused struct fm10k_tx_queue *txq)
 {
 	return;
 }
 
-int __attribute__((weak))
+__rte_weak int
 fm10k_tx_vec_condition_check(__rte_unused struct fm10k_tx_queue *txq)
 {
 	return -1;
 }
 
-uint16_t __attribute__((weak))
+__rte_weak uint16_t
 fm10k_xmit_fixed_burst_vec(__rte_unused void *tx_queue,
 			   __rte_unused struct rte_mbuf **tx_pkts,
 			   __rte_unused uint16_t nb_pkts)
-- 
2.17.1

  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 ` Keith Wiles [this message]
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 ` [dpdk-dev] [PATCH 07/10] mlx5: " Keith Wiles
2018-08-03 17:32   ` 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-4-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).