From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Chen Ni <nichen@iscas.ac.cn>,
mazziesaccount@gmail.com, lars@metafoo.de,
Michael.Hennerich@analog.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: adc: ad7476: Remove duplicate include and sort the rest
Date: Sun, 11 Jan 2026 13:18:14 +0000 [thread overview]
Message-ID: <20260111131814.649cd226@jic23-huawei> (raw)
In-Reply-To: <CAHp75Vdiq0jhRV0SuQ9nT1NvSqnpv=3T6OPOLogkrT3f5kGt8A@mail.gmail.com>
On Thu, 8 Jan 2026 11:22:53 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Thu, Jan 8, 2026 at 10:41 AM Chen Ni <nichen@iscas.ac.cn> wrote:
> >
> > Remove duplicate <linux/bitops.h> and sort all headers alphabetically.
>
> I'm okay with this change, but I think ideally it would be three
> patches in a series:
> patch 1) as your v1;
I picked up v1 for this reason.
> patch 2) sorting the headers (as here);
> patch 3) getting rid of "proxy" headers, e.g. kernel.h, by replacing
> them with what actually is being used.
Absolutely on these being good follow up steps.
>
> > #include <linux/bitops.h>
> > +#include <linux/delay.h>
>
> > #include <linux/device.h>
>
> ^^^ needs to be checked if it's used as a "proxy"
>
> > +#include <linux/err.h>
> > +#include <linux/gpio/consumer.h>
>
> > #include <linux/kernel.h>
>
> ^^^ This is for sure not used as is in the driver, so definitely has
> to be replaced.
>
> > +#include <linux/module.h>
> > +#include <linux/regulator/consumer.h>
> > #include <linux/slab.h>
> > -#include <linux/sysfs.h>
> > #include <linux/spi/spi.h>
> > -#include <linux/regulator/consumer.h>
> > -#include <linux/gpio/consumer.h>
> > -#include <linux/err.h>
> > -#include <linux/module.h>
> > -#include <linux/bitops.h>
> > -#include <linux/delay.h>
> > +#include <linux/sysfs.h>
>
> It's up to the maintainers and to you to resplit, send a v3, but
> again, I'm fine with this version.
I'd prefer the split as you have it above. As such I picked v1 up
to get patch 1 of that split up.
Thanks,
Jonathan
>
prev parent reply other threads:[~2026-01-11 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 8:39 Chen Ni
2026-01-08 9:22 ` Andy Shevchenko
2026-01-11 13:18 ` Jonathan Cameron [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=20260111131814.649cd226@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=nichen@iscas.ac.cn \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®