From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 0/4] fix warnings with gcc 9 on Fedora 30
Date: Thu, 02 May 2019 14:18:51 +0200 [thread overview]
Message-ID: <8175150.iIoqqa2Iee@xps> (raw)
In-Reply-To: <20190501195014.2938-1-bruce.richardson@intel.com>
01/05/2019 21:50, Bruce Richardson:
> This set of changes fixes warnings seen when compiling DPDK on Fedora 30.
> In most cases these warnings appear to be false positives, which means we
> have the option to just disable the warning. Because the changes required
> to the code to silence the warnings are fairly small I've chosen in all cases
> to change the code rather than disable the warnings, but I'm open to doing
> the opposite if it's felt it's a better solution. [One thing I didn't like
> about disabling the warnings is that the disabling flags are not supported
> by clang, so adding them involves compiler checks :-(]
>
> NOTE: this set does not cover all warnings with GCC9, but it does cover
> those seen when building with meson. There is still one warning disable
> flag needed when building with make, which will need a follow-on set to
> fix.
>
> Bruce Richardson (4):
> net/ixgbe: fix warning with GCC 9 on Fedora 30
> bus/fslmc: fix printf of null pointer
> raw/skeleton_rawdev: fix warnings with GCC 9 on Fedora 30
> raw/dpaa2_cmdif: fix warnings with GCC 9 on Fedora 30
Cc: stable@dpdk.org
Applied, thanks
next parent reply other threads:[~2019-05-02 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190501195014.2938-1-bruce.richardson@intel.com>
2019-05-02 12:18 ` Thomas Monjalon [this message]
2019-05-02 12:32 ` David Marchand
2019-05-02 13:24 ` Bruce Richardson
2019-05-02 13:32 ` David Marchand
2019-05-02 13:46 ` Bruce Richardson
2019-05-02 13:53 ` David Marchand
2019-05-02 14:04 ` Bruce Richardson
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=8175150.iIoqqa2Iee@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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).