From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/6] Deal with a bunch of staticFunction warnings from cppcheck 2.17
Date: Fri, 7 Mar 2025 07:30:05 +0100 [thread overview]
Message-ID: <20250307073005.76534e1a@elisabeth> (raw)
In-Reply-To: <20250305061508.1699713-1-david@gibson.dropbear.id.au>
On Wed, 5 Mar 2025 17:15:02 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> The new cppcheck version in Fedora 41 is a bunch more aggressive with
> staticFunction warnings, about exposed functions that aren't used
> outside their .c file. Deal with these warnings.
>
> David Gibson (6):
> treewide: Mark assorted functions static
> log: Don't export passt_vsyslog()
> checksum: Don't export various functions
> tcp: Don't export tcp_update_csum()
> vhost_user: Don't export several functions
> cppcheck: Add suppressions for "logically" exported functions
Applied.
--
Stefano
prev parent reply other threads:[~2025-03-07 6:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:15 [PATCH 0/6] Deal with a bunch of staticFunction warnings from cppcheck 2.17 David Gibson
2025-03-05 6:15 ` [PATCH 1/6] treewide: Mark assorted functions static David Gibson
2025-03-05 6:15 ` [PATCH 2/6] log: Don't export passt_vsyslog() David Gibson
2025-03-05 6:15 ` [PATCH 3/6] checksum: Don't export various functions David Gibson
2025-03-05 6:15 ` [PATCH 4/6] tcp: Don't export tcp_update_csum() David Gibson
2025-03-05 6:15 ` [PATCH 5/6] vhost_user: Don't export several functions David Gibson
2025-03-05 6:15 ` [PATCH 6/6] cppcheck: Add suppressions for "logically" exported functions David Gibson
2025-03-07 6:30 ` Stefano Brivio [this message]
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=20250307073005.76534e1a@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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).