From: Conor Walsh <conor.walsh@intel.com>
To: bruce.richardson@intel.com, ajit.khaparde@broadcom.com,
somnath.kotur@broadcom.com, bluca@debian.org,
stuart.schacher@broadcom.com, venkatkumar.duvvuru@broadcom.com,
michael.wildt@broadcom.com
Cc: dev@dpdk.org, stable@dpdk.org, linglix.chen@intel.com,
thomas@monjalon.net, Conor Walsh <conor.walsh@intel.com>
Subject: [dpdk-stable] [PATCH v3 0/2] build: add Wformat to fix gcc compile warnings and format fixes
Date: Thu, 19 Nov 2020 10:16:58 +0000 [thread overview]
Message-ID: <20201119101700.3869583-1-conor.walsh@intel.com> (raw)
In-Reply-To: <20201118181103.3865787-1-conor.walsh@intel.com>
On some systems Wformat-nonliteral and Wformat-security could not be
checked without Wformat also being specified this causes a compile
warning on these systems. This patchset adds Wformat to
config/meson.build and fixes some format issues that this exposed.
---
v3: add stable@dpdk.org to cc list following list feedback
v2:
- expand explaination of patches
- suppress false postives in icc
- add fixes for format issues
Conor Walsh (2):
build: fix gcc compile warnings by adding wformat
net/bnxt: fix format characters for unsigned values
config/meson.build | 3 ++-
drivers/net/bnxt/tf_core/tf_core.c | 8 ++++----
2 files changed, 6 insertions(+), 5 deletions(-)
--
2.25.1
next parent reply other threads:[~2020-11-19 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201118181103.3865787-1-conor.walsh@intel.com>
2020-11-19 10:16 ` Conor Walsh [this message]
2020-11-19 10:16 ` [dpdk-stable] [PATCH v3 1/2] build: fix gcc compile warnings by adding wformat Conor Walsh
2020-11-20 7:23 ` Chen, LingliX
2020-11-19 10:17 ` [dpdk-stable] [PATCH v3 2/2] net/bnxt: fix format characters for unsigned values Conor Walsh
2020-11-19 23:12 ` Ajit Khaparde
2020-11-22 20:07 ` [dpdk-stable] [PATCH v3 0/2] build: add Wformat to fix gcc compile warnings and format fixes Thomas Monjalon
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=20201119101700.3869583-1-conor.walsh@intel.com \
--to=conor.walsh@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=linglix.chen@intel.com \
--cc=michael.wildt@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=stuart.schacher@broadcom.com \
--cc=thomas@monjalon.net \
--cc=venkatkumar.duvvuru@broadcom.com \
/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).