DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/6] reduce number of warnings being disabled
Date: Wed, 30 Oct 2024 17:38:23 +0000	[thread overview]
Message-ID: <20241030173830.881368-1-bruce.richardson@intel.com> (raw)

for historical reasons, many drivers had extra warnings disabled,
especially in their base code directory. Many, but not all, of these
warning disabling flags are unnecessary so remove as many as we can.

Bruce Richardson (6):
  net/i40e/base: remove warning disable flags
  net/ice/base: remove warning disable flag
  net/e1000/base: remove warning disable flags
  net/iavf: remove warning disable flag
  net/fm10k/base: remove warning disable flags
  common/idpf/base: remove warning disable flags

 drivers/common/idpf/base/meson.build | 13 ++++++++-----
 drivers/net/e1000/base/meson.build   |  7 ++++---
 drivers/net/fm10k/base/meson.build   |  6 +++---
 drivers/net/i40e/base/meson.build    |  9 +++++----
 drivers/net/iavf/meson.build         |  2 --
 drivers/net/ice/base/meson.build     |  1 -
 6 files changed, 20 insertions(+), 18 deletions(-)

--
2.43.0


             reply	other threads:[~2024-10-30 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 17:38 Bruce Richardson [this message]
2024-10-30 17:38 ` [PATCH 1/6] net/i40e/base: remove warning disable flags Bruce Richardson
2024-10-30 17:38 ` [PATCH 2/6] net/ice/base: remove warning disable flag Bruce Richardson
2024-10-30 17:38 ` [PATCH 3/6] net/e1000/base: remove warning disable flags Bruce Richardson
2024-10-30 17:38 ` [PATCH 4/6] net/iavf: remove warning disable flag Bruce Richardson
2024-10-30 17:38 ` [PATCH 5/6] net/fm10k/base: remove warning disable flags Bruce Richardson
2024-10-30 17:38 ` [PATCH 6/6] common/idpf/base: " Bruce Richardson
2024-10-30 18:17 ` [PATCH 0/6] reduce number of warnings being disabled Konstantin Ananyev

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=20241030173830.881368-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --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).