From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: mdshahid03@gmail.com
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com, linux-iio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] iio: adc: bcm_iproc_adc: sort headers alphabetically
Date: Wed, 26 Aug 2026 00:28:22 -0300 [thread overview]
Message-ID: <ao5dVuReF1Q63ccU@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20260825172155.250484-2-mdshahid03@gmail.com>
Hello Mohammad,
On 08/25, mdshahid03@gmail.com wrote:
> From: Mohammad Shahid <mdshahid03@gmail.com>
>
> Sort the Linux kernel headers alphabetically to improve consistency
> and make the include list easier to maintain.
>
> Signed-off-by: Mohammad Shahid <mdshahid03@gmail.com>
> ---
> drivers/iio/adc/bcm_iproc_adc.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/adc/bcm_iproc_adc.c b/drivers/iio/adc/bcm_iproc_adc.c
> index ab66b97d2f04..e46e3761993a 100644
> --- a/drivers/iio/adc/bcm_iproc_adc.c
> +++ b/drivers/iio/adc/bcm_iproc_adc.c
> @@ -3,14 +3,14 @@
> * Copyright 2016 Broadcom
> */
>
> -#include <linux/module.h>
> -#include <linux/io.h>
> #include <linux/clk.h>
> -#include <linux/mfd/syscon.h>
> -#include <linux/regmap.h>
> #include <linux/delay.h>
> #include <linux/interrupt.h>
> +#include <linux/io.h>
> +#include <linux/mfd/syscon.h>
> +#include <linux/module.h>
> #include <linux/platform_device.h>
> +#include <linux/regmap.h>
>
> #include <linux/iio/iio.h>
The sorting looks okay to me. Though, there are some includes missing and a
couple of them that don't seem to be needed (delay.h and io.h). Either in
replacement of this patch or as a follow on extra patch (not sure how maintainers
would like to have it in this case), it would be nice to also update the include
list according to include-what-you-use principles.
If you decide to work on the update to make it iwyu compliant, it may be
helpful to set an IIO tailored mapping file such as the one shared by Jonathan
a while ago.
https://lore.kernel.org/linux-iio/20250629194336.34a03946@jic23-huawei/
next prev parent reply other threads:[~2026-08-26 3:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 17:21 [PATCH v1 0/3] iio: adc: bcm_iproc_adc: Convert to devm-managed resources mdshahid03
2026-08-25 17:21 ` [PATCH v1 1/3] iio: adc: bcm_iproc_adc: sort headers alphabetically mdshahid03
2026-08-26 3:28 ` Marcelo Schmitt [this message]
2026-08-26 8:26 ` Andy Shevchenko
2026-08-25 17:21 ` [PATCH v1 2/3] iio: adc: bcm_iproc_adc: use devm_add_action_or_reset() mdshahid03
2026-08-26 3:33 ` Marcelo Schmitt
2026-08-25 17:21 ` [PATCH v1 3/3] iio: adc: bcm_iproc_adc: use devm-managed mutex initialization mdshahid03
2026-08-26 3:35 ` Marcelo Schmitt
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=ao5dVuReF1Q63ccU@debian-BULLSEYE-live-builder-AMD64 \
--to=marcelo.schmitt1@gmail.com \
--cc=andy@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdshahid03@gmail.com \
--cc=nuno.sa@analog.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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