From: Shawn Guo <shawnguo@kernel.org>
To: Marcel Ziswiler <marcel@ziswiler.com>
Cc: linux-arm-kernel@lists.infradead.org,
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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/5] ARM: dts: imx6sx-udoo-neo: don't use multiple blank lines
Date: Mon, 5 Sep 2022 10:01:24 +0800 [thread overview]
Message-ID: <20220905020124.GY1728671@dragon> (raw)
In-Reply-To: <20220826192252.794651-3-marcel@ziswiler.com>
On Fri, Aug 26, 2022 at 09:22:49PM +0200, Marcel Ziswiler wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> This fixes the following warning:
>
> arch/arm/boot/dts/imx6sx-udoo-neo.dtsi:309: check: Please don't use multiple
> blank lines
It includes changes more than multiple blank lines fix. I mentioned
those indent changes a bit in the commit log.
>
> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Applied, thanks!
Shawn
> ---
>
> arch/arm/boot/dts/imx6sx-udoo-neo.dtsi | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx6sx-udoo-neo.dtsi b/arch/arm/boot/dts/imx6sx-udoo-neo.dtsi
> index 35861bbea94e..c84ea1fac5e9 100644
> --- a/arch/arm/boot/dts/imx6sx-udoo-neo.dtsi
> +++ b/arch/arm/boot/dts/imx6sx-udoo-neo.dtsi
> @@ -226,7 +226,7 @@ lcdc: endpoint {
> &iomuxc {
> pinctrl_bt_reg: btreggrp {
> fsl,pins =
> - <MX6SX_PAD_KEY_ROW2__GPIO2_IO_17 0x15059>;
> + <MX6SX_PAD_KEY_ROW2__GPIO2_IO_17 0x15059>;
> };
>
> pinctrl_enet1: enet1grp {
> @@ -306,7 +306,6 @@ MX6SX_PAD_LCD1_RESET__GPIO3_IO_27 0x4001b0b0
> >;
> };
>
> -
> pinctrl_uart1: uart1grp {
> fsl,pins =
> <MX6SX_PAD_GPIO1_IO04__UART1_DCE_TX 0x1b0b1>,
> @@ -347,24 +346,23 @@ pinctrl_uart6: uart6grp {
>
> pinctrl_otg1_reg: otg1grp {
> fsl,pins =
> - <MX6SX_PAD_GPIO1_IO09__GPIO1_IO_9 0x10b0>;
> + <MX6SX_PAD_GPIO1_IO09__GPIO1_IO_9 0x10b0>;
> };
>
> -
> pinctrl_otg2_reg: otg2grp {
> fsl,pins =
> - <MX6SX_PAD_NAND_RE_B__GPIO4_IO_12 0x10b0>;
> + <MX6SX_PAD_NAND_RE_B__GPIO4_IO_12 0x10b0>;
> };
>
> pinctrl_usb_otg1: usbotg1grp {
> fsl,pins =
> - <MX6SX_PAD_GPIO1_IO10__ANATOP_OTG1_ID 0x17059>,
> - <MX6SX_PAD_GPIO1_IO08__USB_OTG1_OC 0x10b0>;
> + <MX6SX_PAD_GPIO1_IO10__ANATOP_OTG1_ID 0x17059>,
> + <MX6SX_PAD_GPIO1_IO08__USB_OTG1_OC 0x10b0>;
> };
>
> pinctrl_usb_otg2: usbot2ggrp {
> fsl,pins =
> - <MX6SX_PAD_QSPI1A_DATA0__USB_OTG2_OC 0x10b0>;
> + <MX6SX_PAD_QSPI1A_DATA0__USB_OTG2_OC 0x10b0>;
> };
>
> pinctrl_usdhc2: usdhc2grp {
> --
> 2.36.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-05 2:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 19:22 [PATCH v1 0/5] ARM: arm64: dts/clk: imx: indentation permission whitespace cleanup 2 Marcel Ziswiler
2022-08-26 19:22 ` [PATCH v1 1/5] ARM: dts: imx6sl: use tabs for code indent Marcel Ziswiler
2022-09-05 1:57 ` Shawn Guo
2022-08-26 19:22 ` [PATCH v1 2/5] ARM: dts: imx6sx-udoo-neo: don't use multiple blank lines Marcel Ziswiler
2022-09-05 2:01 ` Shawn Guo [this message]
2022-08-26 19:22 ` [PATCH v1 3/5] arm64: dts: imx8ulp: no executable source file permission Marcel Ziswiler
2022-08-29 5:41 ` Peng Fan
2022-09-05 1:53 ` Shawn Guo
2022-08-26 19:22 ` [PATCH v1 4/5] clk: imx6sll: add proper spdx license identifier Marcel Ziswiler
2022-08-29 9:40 ` Abel Vesa
2022-08-30 21:13 ` Rob Herring
2022-09-23 13:28 ` Marcel Ziswiler
2022-08-26 19:22 ` [PATCH v1 5/5] dt-bindings: imx8ulp: clock: no spaces before tabs Marcel Ziswiler
2022-08-27 17:23 ` Krzysztof Kozlowski
2022-08-29 9:40 ` Abel Vesa
2022-09-23 13:29 ` 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=20220905020124.GY1728671@dragon \
--to=shawnguo@kernel.org \
--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=marcel@ziswiler.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).