From: Breno Leitao <leitao@debian.org>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: axboe@kernel.dk, io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: Trim out unused includes
Date: Mon, 12 Jan 2026 04:11:06 -0800 [thread overview]
Message-ID: <wuha2oln3kdumecdsmpttykdq2p5bwp6db3cfoyqoy5ftnedmg@ftlotbrnrev7> (raw)
In-Reply-To: <20260105230932.3805619-1-krisman@suse.de>
Hello Gabriel,
On Mon, Jan 05, 2026 at 06:09:32PM -0500, Gabriel Krisman Bertazi wrote:
> Clean up some left overs of refactoring io_uring into multiple files.
> Compile tested with a few configurations.
Do you have a tool to detect those unused header? I am curious how is
the process to discover unused headers in .c files.
Thanks
--breno
next prev parent reply other threads:[~2026-01-12 12:11 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 [this message]
2026-01-12 14:36 ` Gabriel Krisman Bertazi
2026-01-12 15:39 ` Breno Leitao
2026-01-12 16:20 ` Caleb Sander Mateos
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=wuha2oln3kdumecdsmpttykdq2p5bwp6db3cfoyqoy5ftnedmg@ftlotbrnrev7 \
--to=leitao@debian.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/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