public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel@ziswiler.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 05/12] ARM: dts: imx7d-pico: indent use tabs, no spaces at start of line
Date: Thu, 21 Jul 2022 21:59:28 +0200	[thread overview]
Message-ID: <20220721195936.1082422-6-marcel@ziswiler.com> (raw)
In-Reply-To: <20220721195936.1082422-1-marcel@ziswiler.com>

From: Marcel Ziswiler <marcel.ziswiler@toradex.com>

Avoid the following checkpatch warning:

arch/arm/boot/dts/imx7d-pico.dtsi:44: error: code indent should use tabs
 where possible
arch/arm/boot/dts/imx7d-pico.dtsi:44: warning: please, no spaces at the
 start of a line

Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
---

 arch/arm/boot/dts/imx7d-pico.dtsi | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/arch/arm/boot/dts/imx7d-pico.dtsi b/arch/arm/boot/dts/imx7d-pico.dtsi
index e519897fae08..e0bff39e8d3e 100644
--- a/arch/arm/boot/dts/imx7d-pico.dtsi
+++ b/arch/arm/boot/dts/imx7d-pico.dtsi
@@ -41,7 +41,7 @@ reg_lcd_3v3: regulator-lcd-3v3 {
 		regulator-max-microvolt = <3300000>;
 		gpio = <&gpio1 6 GPIO_ACTIVE_HIGH>;
 		enable-active-high;
-        };
+	};
 
 	reg_wlreg_on: regulator-wlreg_on {
 		compatible = "regulator-fixed";
@@ -432,7 +432,7 @@ MX7D_PAD_ENET1_RGMII_RD1__ENET1_RGMII_RD1	0x1
 			MX7D_PAD_ENET1_RGMII_RD2__ENET1_RGMII_RD2	0x1
 			MX7D_PAD_ENET1_RGMII_RD3__ENET1_RGMII_RD3	0x1
 			MX7D_PAD_ENET1_RGMII_RX_CTL__ENET1_RGMII_RX_CTL	0x1
-			MX7D_PAD_SD3_RESET_B__GPIO6_IO11                0x1  /* Ethernet reset */
+			MX7D_PAD_SD3_RESET_B__GPIO6_IO11		0x1  /* Ethernet reset */
 		>;
 	};
 
@@ -493,19 +493,19 @@ MX7D_PAD_LCD_RESET__GPIO3_IO4		0x14
 
 	pinctrl_pwm1: pwm1 {
 		fsl,pins = <
-			MX7D_PAD_GPIO1_IO08__PWM1_OUT   0x7f
+			MX7D_PAD_GPIO1_IO08__PWM1_OUT	0x7f
 		>;
 	};
 
 	pinctrl_pwm2: pwm2 {
 		fsl,pins = <
-			MX7D_PAD_GPIO1_IO09__PWM2_OUT   0x7f
+			MX7D_PAD_GPIO1_IO09__PWM2_OUT	0x7f
 		>;
 	};
 
 	pinctrl_pwm3: pwm3 {
 		fsl,pins = <
-			MX7D_PAD_GPIO1_IO10__PWM3_OUT   0x7f
+			MX7D_PAD_GPIO1_IO10__PWM3_OUT	0x7f
 		>;
 	};
 
-- 
2.35.1


  parent reply	other threads:[~2022-07-21 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 19:59 [PATCH v1 00/12] ARM: arm64: dts/clk: imx8mm: indentation whitespace cleanup Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 01/12] ARM: dts: imx6-sabrelite: change to use SPDX identifiers Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 02/12] ARM: dts: imx6qdl-mba6: don't use multiple blank lines Marcel Ziswiler
2022-07-22  6:12   ` Alexander Stein
2022-07-21 19:59 ` [PATCH v1 03/12] ARM: dts: imx6qdl: phytec: no spaces at start of line, indent use tabs Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 04/12] ARM: dts: imx6qdl-sabre: change to use SPDX identifiers Marcel Ziswiler
2022-07-21 19:59 ` Marcel Ziswiler [this message]
2022-07-21 19:59 ` [PATCH v1 06/12] ARM: dts: vf610: no spaces in indent but tabs Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 07/12] ARM: dts: vf610-twr: indent use tabs, no spaces at start of line Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 08/12] ARM: dts: vf610: don't use multiple blank lines Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 09/12] arm64: dts: imx8mm-venice-gw72xx-0x: blank line at end of file Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 10/12] arm64: dts: imx8mp-verdin: don't use multiple blank lines Marcel Ziswiler
2022-07-21 19:59 ` [PATCH v1 11/12] arm64: dts: mnt-reform2: " Marcel Ziswiler
2022-07-22 12:37   ` Lucas Stach
2022-07-21 19:59 ` [PATCH v1 12/12] clk: imx8mm: " Marcel Ziswiler

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=20220721195936.1082422-6-marcel@ziswiler.com \
    --to=marcel@ziswiler.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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