public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Peter Foley <pefoley@google.com>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] Add missing includes to headers
Date: Mon, 23 Feb 2026 21:47:45 +0100 (CET)	[thread overview]
Message-ID: <20260223214736.6327e5c7@elisabeth> (raw)
In-Reply-To: <CAAAKUPMRYcbeTXZHX9aQtZfv4L=sBbzqSWqo-xG91F6r7f8M1w@mail.gmail.com>

On Mon, 23 Feb 2026 15:22:20 -0500
Peter Foley <pefoley@google.com> wrote:

> On Mon, Feb 23, 2026 at 2:05 PM Stefano Brivio <sbrivio@redhat.com> wrote:
> 
> > Hmm, "nice". I guess we should find out if it's reasonable / doable to
> > "fix" all those.
>
> I tried just doing clang-include-cleaner --edit, but it's  
> unfortunately c++ centric, so it added a bunch of stuff like <cstdint>
> I can try manually fixing that up and seeing what happens.

By the way, I won't have a chance to try this before a couple of days,
if needed, but another thought: if we end up adding/changing hundreds
of include lines as a result, maybe the cleanup David mentioned would
actually be in scope at that point, even from a mere perspective of
"noise" we would add, or effort you're spending anyway (let's make it
fully worth it I'd say).

In any case we could keep a clean clang-include-cleaner output as
second step.

I think the priorities here should be 1. keep/make things working for
everybody while 2. avoiding the risk of recurring fix-ups for future
changes and 3. make things pretty/readable/elegant, exactly in this
order.

If we can tackle all of them together, great, otherwise we can take
care of 1. first, and 2. and 3. later.

-- 
Stefano


  parent reply	other threads:[~2026-02-23 20:47 UTC|newest]

Thread overview: 9+ 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 [this message]
     [not found]                 ` <CAAAKUPPS8_7gJ1T677djyWJ8WbKSoijKsuM8J1cgLLD5HDPXgw@mail.gmail.com>
2026-02-23 23:00                   ` Stefano Brivio
2026-02-23  5:33 ` David Gibson
2026-02-23 16:32   ` 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=20260223214736.6327e5c7@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).