From: Bastien Curutchet <bastien.curutchet@bootlin.com>
To: Peter Rosin <peda@axentia.se>, Andi Shyti <andi.shyti@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Christopher Cordahi <christophercordahi@nanometrics.ca>,
Bastien Curutchet <bastien.curutchet@bootlin.com>
Subject: [PATCH v3 2/3] i2c: mux: gpio: Re-order #include to match alphabetic order
Date: Mon, 17 Jun 2024 14:08:17 +0200 [thread overview]
Message-ID: <20240617120818.81237-3-bastien.curutchet@bootlin.com> (raw)
In-Reply-To: <20240617120818.81237-1-bastien.curutchet@bootlin.com>
The #includes don't match alphabetic order.
Re-order #includes to match the alphabetic order before adding a new
one.
Signed-off-by: Bastien Curutchet <bastien.curutchet@bootlin.com>
---
drivers/i2c/muxes/i2c-mux-gpio.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/muxes/i2c-mux-gpio.c b/drivers/i2c/muxes/i2c-mux-gpio.c
index d6bbb8b68333..c61e9d9ea695 100644
--- a/drivers/i2c/muxes/i2c-mux-gpio.c
+++ b/drivers/i2c/muxes/i2c-mux-gpio.c
@@ -5,16 +5,16 @@
* Peter Korsgaard <peter.korsgaard@barco.com>
*/
+#include <linux/bits.h>
+#include <linux/gpio/consumer.h>
+#include <linux/gpio/driver.h>
#include <linux/i2c.h>
#include <linux/i2c-mux.h>
+#include <linux/module.h>
#include <linux/overflow.h>
#include <linux/platform_data/i2c-mux-gpio.h>
#include <linux/platform_device.h>
-#include <linux/module.h>
#include <linux/slab.h>
-#include <linux/bits.h>
-#include <linux/gpio/consumer.h>
-#include <linux/gpio/driver.h>
struct gpiomux {
struct i2c_mux_gpio_platform_data data;
--
2.45.0
next prev parent reply other threads:[~2024-06-17 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 12:08 [PATCH v3 0/3] i2c: mux: gpio: Add 'settle-time-us' property Bastien Curutchet
2024-06-17 12:08 ` [PATCH v3 1/3] dt-bindings: i2c: " Bastien Curutchet
2024-06-17 12:19 ` Krzysztof Kozlowski
2024-07-09 21:42 ` Andi Shyti
2024-07-10 8:01 ` Peter Rosin
2024-07-12 7:00 ` Wolfram Sang
2024-06-17 12:08 ` Bastien Curutchet [this message]
2024-07-09 21:42 ` [PATCH v3 2/3] i2c: mux: gpio: Re-order #include to match alphabetic order Andi Shyti
2024-07-10 8:02 ` Peter Rosin
2024-06-17 12:08 ` [PATCH v3 3/3] i2c: mux: gpio: Add support for the 'settle-time-us' property Bastien Curutchet
2024-07-09 21:43 ` Andi Shyti
2024-07-10 8:02 ` Peter Rosin
2024-07-12 6:58 ` Wolfram Sang
2024-07-03 9:35 ` [PATCH v3 0/3] i2c: mux: gpio: Add " Bastien Curutchet
2024-07-09 21:45 ` Andi Shyti
2024-07-10 8:04 ` Peter Rosin
2024-07-16 18:28 ` Andi Shyti
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=20240617120818.81237-3-bastien.curutchet@bootlin.com \
--to=bastien.curutchet@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=christophercordahi@nanometrics.ca \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).