From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v2 3/3] ARM: dts: marvell: orion5x: Correct indentation
Date: Mon, 13 Jul 2026 17:52:22 +0200 [thread overview]
Message-ID: <871pd67uq1.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260706180333.648401-6-krzysztof.kozlowski@oss.qualcomm.com>
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> writes:
> Correct spaces or mix of tabs+spaces into proper tab-indented lines.
> No functional impact (same DTB).
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
Applied on mvebu/dt
Thanks,
Gregory
> ---
>
> Ongoing bigger work for all bindings and DTS with built-in checker (dt-check-style).
> ---
> arch/arm/boot/dts/marvell/orion5x-lacie-d2-network.dts | 2 +-
> arch/arm/boot/dts/marvell/orion5x-maxtor-shared-storage-2.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/marvell/orion5x-lacie-d2-network.dts b/arch/arm/boot/dts/marvell/orion5x-lacie-d2-network.dts
> index 12a4aac2633e..9757c3b57de6 100644
> --- a/arch/arm/boot/dts/marvell/orion5x-lacie-d2-network.dts
> +++ b/arch/arm/boot/dts/marvell/orion5x-lacie-d2-network.dts
> @@ -109,7 +109,7 @@ flash@0 {
> compatible = "cfi-flash";
> reg = <0 0x80000>;
> bank-width = <1>;
> - #address-cells = <1>;
> + #address-cells = <1>;
> #size-cells = <1>;
>
> partition@0 {
> diff --git a/arch/arm/boot/dts/marvell/orion5x-maxtor-shared-storage-2.dts b/arch/arm/boot/dts/marvell/orion5x-maxtor-shared-storage-2.dts
> index cb1bd24b7ae3..b2b3309ed1df 100644
> --- a/arch/arm/boot/dts/marvell/orion5x-maxtor-shared-storage-2.dts
> +++ b/arch/arm/boot/dts/marvell/orion5x-maxtor-shared-storage-2.dts
> @@ -69,7 +69,7 @@ flash@0 {
> compatible = "cfi-flash";
> reg = <0 0x40000>;
> bank-width = <1>;
> - #address-cells = <1>;
> + #address-cells = <1>;
> #size-cells = <1>;
> };
> };
> --
> 2.53.0
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-13 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 18:03 [PATCH v2 1/3] ARM: dts: marvell: armada: Correct indentation Krzysztof Kozlowski
2026-07-06 18:03 ` [PATCH v2 2/3] ARM: dts: marvell: kirkwood: " Krzysztof Kozlowski
2026-07-13 15:52 ` Gregory CLEMENT
2026-07-06 18:03 ` [PATCH v2 3/3] ARM: dts: marvell: orion5x: " Krzysztof Kozlowski
2026-07-13 15:52 ` Gregory CLEMENT [this message]
2026-07-13 15:52 ` [PATCH v2 1/3] ARM: dts: marvell: armada: " Gregory CLEMENT
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=871pd67uq1.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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