From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] test: eal flags cleanup
Date: Sat, 15 Nov 2025 11:33:06 -0800 [thread overview]
Message-ID: <20251115193409.99740-1-stephen@networkplumber.org> (raw)
Revisions to the EAL flags tests to cleanup and fix warnings.
Split off from earlier patch series.
Stephen Hemminger (4):
test: re-enable format-truncation warnings
test: increase size of memzone name
test: refactor file prefix arg handling
test: use unit test runner for eal flags
app/test/meson.build | 1 -
app/test/test_eal_flags.c | 161 ++++++++++++++++----------------------
app/test/test_memzone.c | 2 +-
3 files changed, 67 insertions(+), 97 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-15 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 19:33 Stephen Hemminger [this message]
2025-11-15 19:33 ` [PATCH 1/4] test: re-enable format-truncation warnings Stephen Hemminger
2025-11-15 19:43 ` Stephen Hemminger
2025-11-15 19:33 ` [PATCH 2/4] test: increase size of memzone name Stephen Hemminger
2025-11-15 19:33 ` [PATCH 3/4] test: refactor file prefix arg handling Stephen Hemminger
2025-11-15 19:33 ` [PATCH 4/4] test: use unit test runner for eal flags 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=20251115193409.99740-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).