From: Russell King <rmk+kernel@armlinux.org.uk>
To: linux-i2c@vger.kernel.org
Subject: [PATCH REPOST 03/12] i2c: pxa: re-arrange includes to be in alphabetical order
Date: Mon, 27 Apr 2020 16:08:47 +0100 [thread overview]
Message-ID: <E1jT5NH-0001qy-RW@rmk-PC.armlinux.org.uk> (raw)
In-Reply-To: <20200427150755.GT5827@shell.armlinux.org.uk>
Arrange the includes to be in alphabetical order to help avoid
duplicated includes.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
---
drivers/i2c/busses/i2c-pxa.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/i2c/busses/i2c-pxa.c b/drivers/i2c/busses/i2c-pxa.c
index dc04f064eb81..0354f6f23a7d 100644
--- a/drivers/i2c/busses/i2c-pxa.c
+++ b/drivers/i2c/busses/i2c-pxa.c
@@ -16,21 +16,21 @@
* Dec 2004: Added support for PXA27x and slave device probing [Liam Girdwood]
* Feb 2005: Rework slave mode handling [RMK]
*/
-#include <linux/kernel.h>
-#include <linux/module.h>
-#include <linux/i2c.h>
-#include <linux/init.h>
+#include <linux/clk.h>
#include <linux/delay.h>
+#include <linux/err.h>
#include <linux/errno.h>
+#include <linux/i2c.h>
+#include <linux/init.h>
#include <linux/interrupt.h>
+#include <linux/io.h>
+#include <linux/kernel.h>
+#include <linux/module.h>
#include <linux/of.h>
#include <linux/of_device.h>
#include <linux/platform_device.h>
-#include <linux/err.h>
-#include <linux/clk.h>
-#include <linux/slab.h>
-#include <linux/io.h>
#include <linux/platform_data/i2c-pxa.h>
+#include <linux/slab.h>
struct pxa_reg_layout {
u32 ibmr;
--
2.20.1
next prev parent reply other threads:[~2020-04-27 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191215160444.GB25745@shell.armlinux.org.uk>
[not found] ` <E1igWOT-0005Dp-Sb@rmk-PC.armlinux.org.uk>
2020-01-20 17:03 ` [PATCH 01/12] i2c: pxa: use official address byte helper Peter Rosin
2020-01-20 19:13 ` Russell King - ARM Linux admin
2020-04-27 15:07 ` [PATCH REPOST 00/12] i2c-pxa cleanups Russell King - ARM Linux admin
2020-04-27 15:08 ` [PATCH REPOST 01/12] i2c: pxa: use official address byte helper Russell King
2020-04-27 17:59 ` Russell King - ARM Linux admin
2020-04-27 15:08 ` [PATCH REPOST 02/12] i2c: pxa: remove unneeded includes Russell King
2020-04-27 15:08 ` Russell King [this message]
2020-04-27 15:08 ` [PATCH REPOST 04/12] i2c: pxa: re-arrange functions to flow better Russell King
2020-04-27 15:08 ` [PATCH REPOST 05/12] i2c: pxa: re-arrange register field definitions Russell King
2020-04-27 15:09 ` [PATCH REPOST 06/12] i2c: pxa: add and use definitions for IBMR register Russell King
2020-04-27 15:09 ` [PATCH REPOST 07/12] i2c: pxa: always set fm and hs members for each type Russell King
2020-04-27 15:09 ` [PATCH REPOST 08/12] i2c: pxa: move private definitions to i2c-pxa.c Russell King
2020-04-27 15:09 ` [PATCH REPOST 09/12] i2c: pxa: move DT IDs along side platform IDs Russell King
2020-04-27 15:09 ` [PATCH REPOST 10/12] i2c: pxa: fix i2c_pxa_scream_blue_murder() debug output Russell King
2020-04-27 15:09 ` [PATCH REPOST 11/12] i2c: pxa: clean up decode_bits() Russell King
2020-04-27 15:09 ` [PATCH REPOST 12/12] i2c: pxa: fix i2c_pxa_wait_bus_not_busy() boundary condition Russell King
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=E1jT5NH-0001qy-RW@rmk-PC.armlinux.org.uk \
--to=rmk+kernel@armlinux.org.uk \
--cc=linux-i2c@vger.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).