From: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Andre Muezerie <andremue@linux.microsoft.com>
Subject: [PATCH 0/5] use portable macro for weak linking
Date: Mon, 23 Dec 2024 19:05:47 -0800 [thread overview]
Message-ID: <1735009552-31906-1-git-send-email-andremue@linux.microsoft.com> (raw)
MSVC uses pragmas to indicate weak linking, so the old __rte_weak
attribute needs to made into a macro so that the same syntax can
be used for MSVC and other compilers like gcc.
Andre Muezerie (5):
lib/eal: add portable macro for weak linking
app/test-compress-perf: use portable macro for weak linking
drivers/bus: use portable macro for weak linking
drivers/common: use portable macro for weak linking
drivers/net: use portable macro for weak linking
app/test-compress-perf/main.c | 36 ++++++++++++------------
drivers/bus/auxiliary/auxiliary_common.c | 8 +++---
drivers/common/nitrox/nitrox_device.c | 16 +++++------
drivers/common/qat/qat_qp.c | 4 +--
drivers/net/enic/enic_main.c | 4 +--
drivers/net/fm10k/fm10k_ethdev.c | 32 ++++++++++-----------
drivers/net/hns3/hns3_rxtx.c | 28 +++++++++---------
drivers/net/nfp/nfdk/nfp_nfdk_vec_stub.c | 4 +--
drivers/net/nfp/nfp_rxtx_vec_stub.c | 8 +++---
drivers/net/virtio/virtio_rxtx.c | 8 +++---
drivers/net/virtio/virtio_rxtx_simple.c | 4 +--
lib/eal/include/rte_common.h | 14 ++++++++-
12 files changed, 89 insertions(+), 77 deletions(-)
--
2.47.0.vfs.0.3
next reply other threads:[~2024-12-24 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 3:05 Andre Muezerie [this message]
2024-12-24 3:05 ` [PATCH 1/5] lib/eal: add " Andre Muezerie
2024-12-24 3:05 ` [PATCH 2/5] app/test-compress-perf: use " Andre Muezerie
2024-12-24 3:05 ` [PATCH 3/5] drivers/bus: " Andre Muezerie
2024-12-24 3:05 ` [PATCH 4/5] drivers/common: " Andre Muezerie
2024-12-24 3:05 ` [PATCH 5/5] drivers/net: " Andre Muezerie
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=1735009552-31906-1-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.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).