From: Caio Morais <caiomorais@usp.br>
To: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, michal.simek@amd.com
Cc: Caio Morais <caiomorais@usp.br>,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iio: fix header includes across multiple drivers
Date: Thu, 23 Apr 2026 15:33:41 -0300 [thread overview]
Message-ID: <20260423183349.636757-1-caiomorais@usp.br> (raw)
From: Caio Morais <caiomorais@usp.br>
Remove unnecessary includes and add missing ones as reported by the
include-what-you-use (IWYU) tool.
Files changed:
- drivers/iio/adc/xilinx-xadc-events.c
- drivers/iio/buffer/industrialio-triggered-buffer.c
- drivers/iio/common/st_sensors/st_sensors_i2c.c
- drivers/iio/common/st_sensors/st_sensors_spi.c
Signed-off-by: Caio Morais <caiomorais@usp.br>
---
drivers/iio/adc/xilinx-xadc-events.c | 4 ++--
drivers/iio/buffer/industrialio-triggered-buffer.c | 8 ++++----
drivers/iio/common/st_sensors/st_sensors_i2c.c | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/iio/adc/xilinx-xadc-events.c b/drivers/iio/adc/xilinx-xadc-events.c
index d16e61953..20b796ec7 100644
--- a/drivers/iio/adc/xilinx-xadc-events.c
+++ b/drivers/iio/adc/xilinx-xadc-events.c
@@ -7,11 +7,11 @@
*/
#include <linux/bitmap.h>
-#include <linux/types.h>
#include <linux/errno.h>
-#include <linux/mutex.h>
#include <linux/iio/events.h>
#include <linux/iio/iio.h>
+#include <linux/mutex.h>
+#include <linux/types.h>
#include "xilinx-xadc.h"
diff --git a/drivers/iio/buffer/industrialio-triggered-buffer.c b/drivers/iio/buffer/industrialio-triggered-buffer.c
index 601a26398..5796c9da7 100644
--- a/drivers/iio/buffer/industrialio-triggered-buffer.c
+++ b/drivers/iio/buffer/industrialio-triggered-buffer.c
@@ -5,15 +5,15 @@
*/
#include <linux/errno.h>
-#include <linux/linkage.h>
-#include <linux/module.h>
-#include <linux/stddef.h>
-#include <linux/iio/iio.h>
#include <linux/iio/buffer.h>
#include <linux/iio/buffer_impl.h>
+#include <linux/iio/iio.h>
#include <linux/iio/kfifo_buf.h>
#include <linux/iio/triggered_buffer.h>
#include <linux/iio/trigger_consumer.h>
+#include <linux/linkage.h>
+#include <linux/module.h>
+#include <linux/stddef.h>
/**
* iio_triggered_buffer_setup_ext() - Setup triggered buffer and pollfunc
diff --git a/drivers/iio/common/st_sensors/st_sensors_i2c.c b/drivers/iio/common/st_sensors/st_sensors_i2c.c
index 6ab143498..974e349ae 100644
--- a/drivers/iio/common/st_sensors/st_sensors_i2c.c
+++ b/drivers/iio/common/st_sensors/st_sensors_i2c.c
@@ -10,10 +10,10 @@
#include <linux/device.h>
#include <linux/err.h>
#include <linux/i2c.h>
+#include <linux/iio/iio.h>
#include <linux/linkage.h>
#include <linux/module.h>
#include <linux/regmap.h>
-#include <linux/iio/iio.h>
#include <linux/iio/common/st_sensors_i2c.h>
--
2.54.0
next reply other threads:[~2026-04-23 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:33 Caio Morais [this message]
2026-04-23 18:45 ` [PATCH] iio: fix header includes across multiple drivers David Lechner
2026-04-24 9:45 ` Andy Shevchenko
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=20260423183349.636757-1-caiomorais@usp.br \
--to=caiomorais@usp.br \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=michal.simek@amd.com \
--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