Skip to contentSkip to conversation

spi: ppc4xx: Sort headers

PATCH In review Andy Shevchenko 2 participants 2 messages Sep 2, 2024 SPI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: ppc4xx: Sort headers

Sort the headers in alphabetic order in order to ease the maintenance for this part.

---

As one of the recent patches showed exactly why this change is useful. e3de1d8deb9f ("spi: spi-ppc4xx: Remove duplicate included header file linux/platform_device.h")

 drivers/spi/spi-ppc4xx.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/spi/spi-ppc4xx.c +8 -8
index 2c43b498432f..4a64ea0f596f 100644
@@ -20,21 +20,21 @@
  * during SPI transfers by setting max_speed_hz via the device tree.
  */
 
-#include <linux/module.h>
-#include <linux/sched.h>
-#include <linux/slab.h>
+#include <linux/delay.h>
 #include <linux/errno.h>
-#include <linux/wait.h>
-#include <linux/platform_device.h>
+#include <linux/interrupt.h>
+#include <linux/io.h>
+#include <linux/module.h>
 #include <linux/of_address.h>
 #include <linux/of_platform.h>
-#include <linux/interrupt.h>
-#include <linux/delay.h>
+#include <linux/platform_device.h>
+#include <linux/sched.h>
+#include <linux/slab.h>
+#include <linux/wait.h>
 
 #include <linux/spi/spi.h>
 #include <linux/spi/spi_bitbang.h>
 
-#include <linux/io.h>
 #include <asm/dcr.h>
 #include <asm/dcr-regs.h>
 
Signature · 1 line
2.43.0.rc1.1336.g36b5255a03ac
maintainer
#1 lore raw
Quoted 4 lines · Andy Shevchenko

Sort the headers in alphabetic order in order to ease the maintenance for this part.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: ppc4xx: Sort headers

      commit: e86836883a8a624680f247c7ac200538c6a5ebaa

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark