From: Caleb Sander Mateos <csander@purestorage.com>
To: Breno Leitao <leitao@debian.org>
Cc: Gabriel Krisman Bertazi <krisman@suse.de>,
axboe@kernel.dk, io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: Trim out unused includes
Date: Mon, 12 Jan 2026 08:20:33 -0800 [thread overview]
Message-ID: <CADUfDZqe+2FB0mM7D5WH1nonrCnhS54C9iq3ofTw-45F6_njNg@mail.gmail.com> (raw)
In-Reply-To: <peuwrn3dswaomm4aqglv2injqbvkmmzw7ost6js5pxvb3ahlu6@23z6cqmrvj5e>
There is a tool "Include What You Use"
(https://github.com/include-what-you-use/include-what-you-use) that
can be used to automate removing unused includes, among other things.
I've used it in other codebases, though never tried it on Linux.
Best,
Caleb
On Mon, Jan 12, 2026 at 7:46 AM Breno Leitao <leitao@debian.org> wrote:
>
> On Mon, Jan 12, 2026 at 09:36:23AM -0500, Gabriel Krisman Bertazi wrote:
> > Breno Leitao <leitao@debian.org> writes:
> >
> > > Do you have a tool to detect those unused header? I am curious how is
> > > the process to discover unused headers in .c files.
> >
> > No. I noticed one that was obviously wrong and that caused me to
> > manually walk over the rest that looked suspicious. I probably missed
> > some in the process.
>
> That is fair, I do the same for my code as well.
>
> Thanks
> --breno
>
prev parent reply other threads:[~2026-01-12 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 23:09 [PATCH] io_uring: Trim out unused includes Gabriel Krisman Bertazi
2026-01-06 0:13 ` Jens Axboe
2026-01-12 12:11 ` Breno Leitao
2026-01-12 14:36 ` Gabriel Krisman Bertazi
2026-01-12 15:39 ` Breno Leitao
2026-01-12 16:20 ` Caleb Sander Mateos [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=CADUfDZqe+2FB0mM7D5WH1nonrCnhS54C9iq3ofTw-45F6_njNg@mail.gmail.com \
--to=csander@purestorage.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
--cc=leitao@debian.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox