From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC 0/8] Avoid overlapping declarations
Date: Wed, 27 Aug 2025 16:14:03 -0700 [thread overview]
Message-ID: <20250827231528.236172-1-stephen@networkplumber.org> (raw)
This is first part of changes to fix places where a variable
declaration overlaps another. These get shown if -Wshadow
is enabled. Lots of drivers and eventdev still have
this problem.
Stephen Hemminger (8):
test/ring: avoid shadow variable usage
test/table: replace conflicting variable name
eal: add macro to disable shadow warnings
eal: avoid shadowed variable aligned_end
eal: avoid shadowed variables in trace code
ethdev: avoid shadowed variable warnings
telemetry: avoid potential name conflict for handler
pcapng: avoid shadow declaration warning
app/test/test_ring.c | 190 +++++++++++++++---------------
app/test/test_table.c | 2 +-
app/test/test_table.h | 2 +-
app/test/test_table_acl.c | 28 ++---
app/test/test_table_pipeline.c | 22 ++--
lib/eal/common/eal_common_trace.c | 42 +++----
lib/eal/common/malloc_heap.c | 6 +-
lib/eal/include/rte_common.h | 17 +++
lib/ethdev/ethdev_driver.c | 2 +-
lib/ethdev/ethdev_driver.h | 6 +-
lib/ethdev/rte_ethdev.c | 1 -
lib/pcapng/rte_pcapng.c | 9 +-
lib/telemetry/rte_telemetry.h | 2 +-
lib/telemetry/telemetry.c | 2 +-
14 files changed, 173 insertions(+), 158 deletions(-)
--
2.47.2
next reply other threads:[~2025-08-27 23:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 23:14 Stephen Hemminger [this message]
2025-08-27 23:14 ` [RFC 1/8] test/ring: avoid shadow variable usage Stephen Hemminger
2025-08-28 7:42 ` Bruce Richardson
2025-08-27 23:14 ` [RFC 2/8] test/table: replace conflicting variable name Stephen Hemminger
2025-08-27 23:14 ` [RFC 3/8] eal: add macro to disable shadow warnings Stephen Hemminger
2025-08-28 7:43 ` Bruce Richardson
2025-08-27 23:14 ` [RFC 4/8] eal: avoid shadowed variable aligned_end Stephen Hemminger
2025-08-27 23:14 ` [RFC 5/8] eal: avoid shadowed variables in trace code Stephen Hemminger
2025-08-27 23:14 ` [RFC 6/8] ethdev: avoid shadowed variable warnings Stephen Hemminger
2025-08-27 23:14 ` [RFC 7/8] telemetry: avoid potential name conflict for handler Stephen Hemminger
2025-08-28 7:45 ` Bruce Richardson
2025-08-27 23:14 ` [RFC 8/8] pcapng: avoid shadow declaration warning Stephen Hemminger
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=20250827231528.236172-1-stephen@networkplumber.org \
--to=stephen@networkplumber.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).