From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1802] bnxt PMD potential name conflicts
Date: Wed, 15 Oct 2025 22:42:54 +0000 [thread overview]
Message-ID: <bug-1802-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1802
Bug ID: 1802
Summary: bnxt PMD potential name conflicts
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The bnxt PMD exposes lots of symbols which do not use consistent prefix of
bnxt_ which could cause conflicts with user code and other PMD's when
statically linked.
bnxt :
0000000000000008 B mpc
00000000000002a0 D fec_mode
00000000000000c0 D link_speeds2_tbl
0000000000000000 D link_speeds_tbl
00000000000002e0 D link_status_str
0000000000000300 D media_type
0000000000000280 D signal_mode
0000000000007570 T vf_vnic_set_rxmask_cb
0000000000000050 T hweight32
0000000000000000 B bit
0000000000000000 D lfsr
0000000000000000 T rand16
0000000000000040 T rand32
0000000000000060 T rand_init
00000000000000f0 T stack_dump
0000000000000000 T stack_init
0000000000000050 T stack_is_empty
0000000000000060 T stack_is_full
0000000000000030 T stack_items
00000000000000b0 T stack_pop
0000000000000070 T stack_push
0000000000000040 T stack_size
0000000000000000 D mod_data
0000000000000370 T next_pow2
0000000000000390 T prev_pow2
00000000000003b0 T roundup32
00000000000003c0 T roundup64
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-10-15 22:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1802-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).