From: "Maxwell Doose" <maxwell@maxwelld.cc>
To: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Maxwell Doose" <maxwell@maxwelld.cc>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"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: Thu, 13 Aug 2026 21:47:00 -0500 [thread overview]
Message-ID: <DKOBND0GKI21.2843OFKP0KR40@maxwelld.cc> (raw)
In-Reply-To: <CAHp75VdDgBcieBdd9q2u75oFCu+w5tAF_L3YNHV5Ra5biHxcsg@mail.gmail.com>
On Thu Aug 13, 2026 at 3:47 PM CDT
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Thu, Aug 13, 2026 at 8:52 PM Maxwell Doose <maxwell@maxwelld.cc> wrote:
>> On Thu Aug 13, 2026 at 2:16 AM CDT
>> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>
> ...
>
>> > -#include <linux/kernel.h>
>> > #include <linux/i2c.h>
>> > #include <linux/errno.h>
>> > #include <linux/delay.h>
>> > +#include <linux/kernel.h>
>>
>> Stray change? The ordering's messed up (seems to be case for many of
>> these drivers) so perhaps we can send a patch to fix the ordering.
>
> Not really. I understand what you mean, but I took a step just for the
> k*.h letter to group them. It's slightly easier to follow with
Fair enough :)
> kernel.h being moved. Note, that kernel.h shouldn't be there at all,
> but that is definitely out of scope here.
Makes sense. I wonder if it may be worth doing a patch series removing
all of the kernel.h inclusions in IIO all at once (or maybe some drivers
have a legitimate use for it, but that seems highly unlikely).
thanks,
max
>
>> > +#include <linux/kstrtox.h>
>> > #include <linux/string.h>
>> > #include <linux/mutex.h>
>> > #include <linux/unistd.h>
>
> Thanks for the review!
next prev parent reply other threads:[~2026-08-14 2:47 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 [this message]
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
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=DKOBND0GKI21.2843OFKP0KR40@maxwelld.cc \
--to=maxwell@maxwelld.cc \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.