From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v2 0/2] LLVM 18.1.1 / Fedora 40 clang-tidy fixes
Date: Tue, 14 May 2024 00:57:56 +1000 [thread overview]
Message-ID: <20240513145758.713647-1-david@gibson.dropbear.id.au> (raw)
A new clang-tidy has introduce some new warnings.
David Gibson (2):
conf: Fix clang-tidy warning about using an undefined enum value
clang-tidy: Suppress macro to enum conversion warnings
Makefile | 9 ++++++++-
conf.c | 4 ++--
fwd.h | 1 +
3 files changed, 11 insertions(+), 3 deletions(-)
--
2.45.0
next reply other threads:[~2024-05-13 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 14:57 David Gibson [this message]
2024-05-13 14:57 ` [PATCH v2 1/2] conf: Fix clang-tidy warning about using an undefined enum value David Gibson
2024-05-13 14:57 ` [PATCH v2 2/2] clang-tidy: Suppress macro to enum conversion warnings David Gibson
2024-05-13 21:36 ` Stefano Brivio
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=20240513145758.713647-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).