public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v2 0/1] Some more static checker fixes
Date: Sat,  8 Jun 2024 16:30:39 +1000	[thread overview]
Message-ID: <20240608063040.1835930-1-david@gibson.dropbear.id.au> (raw)

This series includes a number of fixes related to the static checkers:

 * Fedora 40 has updated to Cppcheck 2.14.1 which introduces some new
   warnings.  Fix them.

 * Jon's recent patch caused a small cppcheck regression.  I assume
   neither Jon nor Stefano is using sufficiently recent cppcheck
   versions to catch it.  Fix that too.

 * We were disabling the bugprone-macro parentheses check in
   clang-tidy.  I don't think that's a good idea.  Re-enable it and
   fix existing warnings.

 * It might also be a good idea to enable the
   bugprone-narrowing-conversions check.  Fix a number of issues
   across the tree which, amongst other things trigger that warning.
   There are lots of other places that trigger the warning which I
   haven't fixed yet, so don't enable it yet.

Changes since v2:
 * Rebased after most of the series was applied
 * Avoid triggering unmatchedSuppression on earlier cppcheck versions

David Gibson (1):
  cppcheck: Suppress constParameterCallback errors

 pasta.c      | 1 +
 tcp.c        | 1 +
 tcp_splice.c | 1 +
 3 files changed, 3 insertions(+)

-- 
2.45.2


             reply	other threads:[~2024-06-08  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-08  6:30 David Gibson [this message]
2024-06-08  6:30 ` [PATCH v2 1/1] cppcheck: Suppress constParameterCallback errors David Gibson

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=20240608063040.1835930-1-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).