From: Joshua Crofts <joshua.crofts1@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>, "Crt Mori" <cmo@melexis.com>,
"Puranjay Mohan" <puranjay@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/14] iio: temperature: make headers conform to IWYU
Date: Sat, 22 Aug 2026 10:17:30 +0200 [thread overview]
Message-ID: <20260822101730.24b93e62@systembl0wer> (raw)
In-Reply-To: <20260822-kernel-header-removal-v1-0-ee31b124be11@gmail.com>
On Sat, 22 Aug 2026 10:02:27 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> This series removes any instances of kernel.h in the temperature/
> subdirectory and cleans up the headers in order to improve readability
> and enforce IYWU instead of relying on transitive dependencies during
> the build process.
>
> I had Gemini generate a summary (a bit more verbose) of changed headers
> under the --- in each IWYU patch to improve the review process.
>
> This is part of an ongoing effort to remove kernel.h entirely from IIO.
>
Okay, initial Sashiko review came back and I've missed a couple more
headers... will have to send a v2.
--
Kind regards,
Joshua Crofts
prev parent reply other threads:[~2026-08-22 8:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 8:02 Joshua Crofts
2026-08-22 8:02 ` [PATCH 01/14] iio: temperature: iqs620at-temp: separate IIO header from others Joshua Crofts
2026-08-22 8:02 ` [PATCH 02/14] iio: temperature: iqs620at-temp: make headers conform to IWYU Joshua Crofts
2026-08-22 8:02 ` [PATCH 03/14] iio: temperature: ltc2983: reorder headers Joshua Crofts
2026-08-22 8:02 ` [PATCH 04/14] iio: temperature: ltc2983: make headers conform to IWYU Joshua Crofts
2026-08-23 17:52 ` Jonathan Cameron
2026-08-24 8:27 ` Andy Shevchenko
2026-08-24 8:36 ` Joshua Crofts
2026-08-22 8:02 ` [PATCH 05/14] iio: temperature: mlx90632: sort headers alphabetically Joshua Crofts
2026-08-23 17:54 ` Jonathan Cameron
2026-08-22 8:02 ` [PATCH 06/14] iio: temperature: mlx90632: make headers conform to IWYU Joshua Crofts
2026-08-22 8:02 ` [PATCH 07/14] iio: temperature: mlx90635: sort headers alphabetically Joshua Crofts
2026-08-22 8:02 ` [PATCH 08/14] iio: temperature: mlx90635: make headers conform to IWYU Joshua Crofts
2026-08-22 8:02 ` [PATCH 09/14] iio: temperature: tmp117: sort headers alphabetically Joshua Crofts
2026-08-22 8:02 ` [PATCH 10/14] iio: temperature: tmp117: make headers conform to IWYU Joshua Crofts
2026-08-22 8:02 ` [PATCH 11/14] iio: temperature: tsys01: reorder headers Joshua Crofts
2026-08-23 17:58 ` Jonathan Cameron
2026-08-22 8:02 ` [PATCH 12/14] iio: temperature: tsys01: make headers conform to IWYU Joshua Crofts
2026-08-22 8:02 ` [PATCH 13/14] iio: temperature: tsys02d: reorder headers Joshua Crofts
2026-08-22 8:02 ` [PATCH 14/14] iio: temperature: tsys02d: make headers conform to IWYU Joshua Crofts
2026-08-22 8:17 ` Joshua Crofts [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=20260822101730.24b93e62@systembl0wer \
--to=joshua.crofts1@gmail.com \
--cc=andy@kernel.org \
--cc=cmo@melexis.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=puranjay@kernel.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
all inboxes | Powered by JetHome®