From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/3] Fix warnings when using gcc 15
Date: Mon, 20 Jan 2025 15:23:37 -0800 [thread overview]
Message-ID: <20250120232442.505866-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20250110170603.538756-1-stephen@networkplumber.or>
Three fixes need to make current main branch build cleanly with
current pre-release of Gcc 15.
Stephen Hemminger (3):
crypto/cnxk: fix gcc 15 warning
net/thunderx/base: fix build with Gcc 15
examples/flow_filtering: fix gcc 15 overflow warning
drivers/crypto/cnxk/cnxk_se.h | 2 +-
drivers/net/thunderx/base/nicvf_mbox.c | 42 +++++++++----------
.../snippets/snippet_match_mpls.c | 2 +-
3 files changed, 23 insertions(+), 23 deletions(-)
--
2.45.2
next parent reply other threads:[~2025-01-20 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250110170603.538756-1-stephen@networkplumber.or>
2025-01-20 23:23 ` Stephen Hemminger [this message]
2025-01-20 23:23 ` [PATCH v2 1/3] crypto/cnxk: fix gcc 15 warning Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 2/3] net/thunderx/base: fix build with Gcc 15 Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 3/3] examples/flow_filtering: fix gcc 15 overflow 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=20250120232442.505866-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).