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 1/3] ARM: dts: marvell: armada: Correct indentation
Date: Mon, 13 Jul 2026 17:52:01 +0200 [thread overview]
Message-ID: <877bmy7uqm.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260706180333.648401-4-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/armada-370.dtsi | 8 ++++----
> arch/arm/boot/dts/marvell/armada-xp-gp.dts | 14 +++++++-------
> 2 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm/boot/dts/marvell/armada-370.dtsi b/arch/arm/boot/dts/marvell/armada-370.dtsi
> index 2013a5ccecd3..cf73287501da 100644
> --- a/arch/arm/boot/dts/marvell/armada-370.dtsi
> +++ b/arch/arm/boot/dts/marvell/armada-370.dtsi
> @@ -63,8 +63,8 @@ pcie0: pcie@1,0 {
> interrupt-names = "intx";
> interrupts-extended = <&mpic 58>;
> #interrupt-cells = <1>;
> - ranges = <0x82000000 0 0 0x82000000 0x1 0 1 0
> - 0x81000000 0 0 0x81000000 0x1 0 1 0>;
> + ranges = <0x82000000 0 0 0x82000000 0x1 0 1 0
> + 0x81000000 0 0 0x81000000 0x1 0 1 0>;
> bus-range = <0x00 0xff>;
> interrupt-map-mask = <0 0 0 7>;
> interrupt-map = <0 0 0 1 &pcie0_intc 0>,
> @@ -91,8 +91,8 @@ pcie2: pcie@2,0 {
> interrupt-names = "intx";
> interrupts-extended = <&mpic 62>;
> #interrupt-cells = <1>;
> - ranges = <0x82000000 0 0 0x82000000 0x2 0 1 0
> - 0x81000000 0 0 0x81000000 0x2 0 1 0>;
> + ranges = <0x82000000 0 0 0x82000000 0x2 0 1 0
> + 0x81000000 0 0 0x81000000 0x2 0 1 0>;
> bus-range = <0x00 0xff>;
> interrupt-map-mask = <0 0 0 7>;
> interrupt-map = <0 0 0 1 &pcie2_intc 0>,
> diff --git a/arch/arm/boot/dts/marvell/armada-xp-gp.dts b/arch/arm/boot/dts/marvell/armada-xp-gp.dts
> index d1d348b91c0a..65cc0373fe04 100644
> --- a/arch/arm/boot/dts/marvell/armada-xp-gp.dts
> +++ b/arch/arm/boot/dts/marvell/armada-xp-gp.dts
> @@ -34,13 +34,13 @@ chosen {
> memory@0 {
> device_type = "memory";
> /*
> - * 8 GB of plug-in RAM modules by default.The amount
> - * of memory available can be changed by the
> - * bootloader according the size of the module
> - * actually plugged. However, memory between
> - * 0xF0000000 to 0xFFFFFFFF cannot be used, as it is
> - * the address range used for I/O (internal registers,
> - * MBus windows).
> + * 8 GB of plug-in RAM modules by default.The amount
> + * of memory available can be changed by the
> + * bootloader according the size of the module
> + * actually plugged. However, memory between
> + * 0xF0000000 to 0xFFFFFFFF cannot be used, as it is
> + * the address range used for I/O (internal registers,
> + * MBus windows).
> */
> reg = <0x00000000 0x00000000 0x00000000 0xf0000000>,
> <0x00000001 0x00000000 0x00000001 0x00000000>;
> --
> 2.53.0
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
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
2026-07-13 15:52 ` Gregory CLEMENT [this message]
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=877bmy7uqm.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