From: Joshua Crofts <joshua.crofts1@gmail.com>
To: "Maxwell Doose" <maxwell@maxwelld.cc>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Marius Cristea" <marius.cristea@microchip.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Tomasz Duszynski" <tduszyns@gmail.com>,
"Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH v1 1/4] iio: light: Unshadow error codes in ->store()
Date: Tue, 18 Aug 2026 16:11:15 +0200 [thread overview]
Message-ID: <20260818161115.000067a4@gmail.com> (raw)
In-Reply-To: <DKRGHVP0FO9A.1VS4B0R21J97C@maxwelld.cc>
On Mon, 17 Aug 2026 14:12:56 -0500
"Maxwell Doose" <maxwell@maxwelld.cc> wrote:
...
> > Absolutely. One patch per driver for this and not more than 10 ish
> > drivers in a series or out for review at a tiem. This stuff is still quite
> > tricky to review, even with details on why each header change below the ---
> >
> > Also precursor patches for any significant reordering to put them in alphabetical
> > + block for IIO headers just to make it easier to read the patch that cleans
> > up what is included.
> >
> > I've done some of these as have many others. It's worthy work but slow to
> > do! I'd suggest we leave it as a newbie task, but it requires more understanding
> > than typical for one of those - so if you want to take it on (probably take
> > a year or more to finish given review bandwidth!) then that would be most
> > welcome.
> >
>
> What we ought to do is start by removing all of the kernel.h inclusions
> and then we can go into each individual driver and do IWYU on them. Not
> sure if we want all of the IWYU stuff (including kernel.h removal)
> rolled up into one patch per driver or if we want to split patches into
> kernel.h removal and then IWYU (hopefully this time I can get iwyu-tool
> setup so it won't be *as* gruelling). Or in the case of we leave it as a
> newbie task maybe we just add it to the TODO (since this is probably one
> of those things that happens over time when we revisit drivers).
Well, removing kernel.h is essentially IWYU, as we have to include the actual
used headers we were pulling in transitively. It should definitely be a task
for newcomers, nevertheless as Jonathan says it's not exactly easy to do from
the get go (and automating it with iwyu-tool can also be a headache). Also,
I've had a pretty good experience with AI when it comes to verifying headers.
I'll probably send a series removing it from some sensor type subdirectory,
just to get the ball rolling?
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-08-18 14:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 7:16 [PATCH v1 0/4] iio: Unshadow error codes in ->store() Andy Shevchenko
2026-08-13 7:16 ` [PATCH v1 1/4] iio: light: " Andy Shevchenko
2026-08-13 17:51 ` Maxwell Doose
2026-08-13 20:47 ` Andy Shevchenko
2026-08-14 2:47 ` Maxwell Doose
2026-08-14 8:14 ` Andy Shevchenko
2026-08-14 8:25 ` Joshua Crofts
2026-08-14 8:50 ` Andy Shevchenko
2026-08-17 2:54 ` Jonathan Cameron
2026-08-17 19:12 ` Maxwell Doose
2026-08-18 14:11 ` Joshua Crofts [this message]
2026-08-13 7:16 ` [PATCH v1 2/4] iio: imu: inv_mpu6050: " Andy Shevchenko
2026-08-13 17:57 ` Maxwell Doose
2026-08-13 20:48 ` Andy Shevchenko
2026-08-13 7:16 ` [PATCH v1 3/4] iio: chemical: sps30: " Andy Shevchenko
2026-08-13 17:53 ` Maxwell Doose
2026-08-13 7:16 ` [PATCH v1 4/4] iio: adc: pac1934: " Andy Shevchenko
2026-08-13 12:17 ` Marius.Cristea
2026-08-13 17:54 ` Maxwell Doose
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=20260818161115.000067a4@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=maxwell@maxwelld.cc \
--cc=nuno.sa@analog.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tduszyns@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox