From: Stefano Brivio <sbrivio@redhat.com>
To: Peter Foley <pefoley@google.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, passt-dev@passt.top
Subject: Re: [PATCH] Add missing includes to headers
Date: Tue, 24 Feb 2026 21:03:18 +0100 (CET) [thread overview]
Message-ID: <20260224210317.585fe9e8@elisabeth> (raw)
In-Reply-To: <CAAAKUPOJhP2OvEyh6BJq8OUviv3UC-ev5ybvqprYkEVif1Carg@mail.gmail.com>
On Tue, 24 Feb 2026 13:52:04 -0500
Peter Foley <pefoley@google.com> wrote:
> On Tue, Feb 24, 2026 at 12:53 PM Stefano Brivio <sbrivio@redhat.com> wrote:
>
> >
> > What I was suggesting was to sprinkle the code with beauties such as:
> >
> > /* NOLINTNEXTLINE(misc-include-cleaner) */
> >
>
> Unfortunatly it needs to go before the usage, not the include.
Ah, right, of course.
> > before each "offending" include line... assuming it works, and
> > assuming we need perhaps 20-30 of them. But if it's a lot more, then
> > that's not a reasonable option either.
>
> I get "72 warnings treated as errors" when running clang-tidy with my
> current set of patches.
Ugh. Yet another alternative could be to enable misc-include-cleaner for
headers only, which would probably need a separate invocation of
clang-tidy.
I'm not sure if that will work at all though. If it doesn't, I'm out of
ideas... maybe we should simply go back to your original patch, in that
case, and you'll just get to "fix" things as they break (hopefully
infrequently) in the future.
--
Stefano
next prev parent reply other threads:[~2026-02-24 20:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 17:45 Peter Foley
2026-02-21 17:57 ` Stefano Brivio
[not found] ` <CAAAKUPN=GPDp84tQAv4Kpxs-AzKR44pDkWda-AbXWaUomYN5eg@mail.gmail.com>
[not found] ` <CAAAKUPMP8goRHqk0VDn6UDWmyyPXpzs37UuCLL8x7wDp10tY6A@mail.gmail.com>
2026-02-23 17:35 ` Stefano Brivio
[not found] ` <CAAAKUPMQZetb9RYoxaUZGyp7dWm8pifmvEfyV3M4Q6+j9jw89g@mail.gmail.com>
2026-02-23 18:11 ` [PATCH v2] " Peter Foley
2026-02-23 19:05 ` [PATCH] " Stefano Brivio
[not found] ` <CAAAKUPMRYcbeTXZHX9aQtZfv4L=sBbzqSWqo-xG91F6r7f8M1w@mail.gmail.com>
2026-02-23 20:47 ` Stefano Brivio
[not found] ` <CAAAKUPPS8_7gJ1T677djyWJ8WbKSoijKsuM8J1cgLLD5HDPXgw@mail.gmail.com>
2026-02-23 23:00 ` Stefano Brivio
2026-02-24 5:43 ` David Gibson
2026-02-24 9:32 ` Stefano Brivio
[not found] ` <CAAAKUPMWQ2t5zT5-rZjvFDaEOSiA44mW9md25i58SDhE=YOMxA@mail.gmail.com>
2026-02-24 17:53 ` Stefano Brivio
[not found] ` <CAAAKUPOJhP2OvEyh6BJq8OUviv3UC-ev5ybvqprYkEVif1Carg@mail.gmail.com>
2026-02-24 20:03 ` Stefano Brivio [this message]
[not found] ` <CAAAKUPM6j6paYFMJgNpzj7RbsAzradSjpb166_epih9DN=3CnA@mail.gmail.com>
2026-02-24 21:18 ` Stefano Brivio
[not found] ` <CAAAKUPNo7z-jbFKTcMdTeVyAKz7nfwQm2sMeY30xU7KRJO5vuw@mail.gmail.com>
2026-02-24 22:49 ` Stefano Brivio
2026-02-25 23:23 ` David Gibson
2026-02-23 5:33 ` David Gibson
2026-02-23 16:32 ` Stefano Brivio
2026-02-24 5:37 ` 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=20260224210317.585fe9e8@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pefoley@google.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).