From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: mvebu: Fix whitespace in armada-xp-98dx3236.dtsi
Date: Tue, 31 Jan 2017 12:12:44 +0100 [thread overview]
Message-ID: <8737fz1o0j.fsf@free-electrons.com> (raw)
In-Reply-To: <20170131034209.3848-1-chris.packham@alliedtelesis.co.nz> (Chris Packham's message of "Tue, 31 Jan 2017 16:42:09 +1300")
Hi Chris,
On mar., janv. 31 2017, Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
> Change sequences of 8 spaces to hard-tabs.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Here again I directly squashed this patch in "ARM: dts: mvebu: Add
device tree for 98DX3236 SoCs". By the way I also fixed the topic, as
for device tree files the topic must start by "ARM: dts: "
Thanks,
Gregory
> ---
> I think this crept in during review and I didn't notice. The file is new enough
> that we shouldn't lose any useful history.
>
> arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm/boot/dts/armada-xp-98dx3236.dtsi b/arch/arm/boot/dts/armada-xp-98dx3236.dtsi
> index 9461128fae24..f6a03dcee5ef 100644
> --- a/arch/arm/boot/dts/armada-xp-98dx3236.dtsi
> +++ b/arch/arm/boot/dts/armada-xp-98dx3236.dtsi
> @@ -201,13 +201,13 @@
> #size-cells = <1>;
> ranges = <0 MBUS_ID(0x08, 0x00) 0 0x100000>;
>
> - dfx_coredivclk: corediv-clock@f8268 {
> - compatible = "marvell,mv98dx3236-corediv-clock";
> - reg = <0xf8268 0xc>;
> - #clock-cells = <1>;
> - clocks = <&mainpll>;
> - clock-output-names = "nand";
> - };
> + dfx_coredivclk: corediv-clock@f8268 {
> + compatible = "marvell,mv98dx3236-corediv-clock";
> + reg = <0xf8268 0xc>;
> + #clock-cells = <1>;
> + clocks = <&mainpll>;
> + clock-output-names = "nand";
> + };
>
> dfx: dfx@0 {
> compatible = "marvell,dfx-server";
> --
> 2.11.0.24.ge6920cf
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2017-01-31 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 3:42 Chris Packham
2017-01-31 11:12 ` 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=8737fz1o0j.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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
Powered by JetHome