From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/7] Fix build with gcc-16
Date: Sun, 28 Dec 2025 10:40:13 -0800 [thread overview]
Message-ID: <20251228184300.541639-1-stephen@networkplumber.org> (raw)
This is a collection of previous patches and a couple of new
ones which allow building DPDK with latesg Gcc 16.
Stephen Hemminger (7):
pcapng: use alloca instead of fixed buffer
pcapng: add additional mbuf if space required on copy
test: add more tests for comments in pcapng
test: vary size of packets in pcapng test
net/bnxt: fix uninitialized warning
common/cnxk: fix array out of bounds
examples/fips_validation: avoid rte_memcpy alignment restriction
app/test/test_pcapng.c | 116 +-
drivers/common/cnxk/roc_nix_inl_dev.c | 10 +-
drivers/net/bnxt/tf_ulp/ulp_mapper.c | 5 +
drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c | 4 +
examples/fips_validation/#main.c# | 3082 ++++++++++++++++++++++
examples/fips_validation/main.c | 14 +-
lib/pcapng/rte_pcapng.c | 38 +-
7 files changed, 3212 insertions(+), 57 deletions(-)
create mode 100644 examples/fips_validation/#main.c#
--
2.51.0
next reply other threads:[~2025-12-28 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 18:40 Stephen Hemminger [this message]
2025-12-28 18:40 ` [PATCH 1/7] pcapng: use alloca instead of fixed buffer Stephen Hemminger
2025-12-28 18:40 ` [PATCH 2/7] pcapng: add additional mbuf if space required on copy Stephen Hemminger
2025-12-28 18:40 ` [PATCH 3/7] test: add more tests for comments in pcapng Stephen Hemminger
2025-12-28 18:40 ` [PATCH 4/7] test: vary size of packets in pcapng test Stephen Hemminger
2025-12-28 18:40 ` [PATCH 5/7] net/bnxt: fix uninitialized warning Stephen Hemminger
2025-12-28 18:40 ` [PATCH 6/7] common/cnxk: fix array out of bounds Stephen Hemminger
2025-12-28 18:40 ` [PATCH 7/7] examples/fips_validation: avoid rte_memcpy alignment restriction 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=20251228184300.541639-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).