From: Rask Ingemann Lambertsen <rask@formelder.dk>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi
Date: Sun, 26 Feb 2017 09:55:54 +0100 [thread overview]
Message-ID: <20170226085553.b6o6mv7ibe5op4dg@localhost> (raw)
In-Reply-To: <20170226011956.53581-7-icenowy@aosc.xyz>
On Sun, Feb 26, 2017 at 09:19:55AM +0800, Icenowy Zheng wrote:
> From: Andre Przywara <andre.przywara@arm.com>
>
> The Allwinner H5 SoC is pin-compatible to the H3 SoC, but uses
> Cortex-A53 cores instead.
> Based on the now shared base .dtsi describing the common peripherals
> describe the H5 specific nodes on top of that.
> That symlinks in the sunxi-h3-h5.dtsi from the arch/arm tree.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> [Icenowy: add H5 pinctrl compatible, and changes for my h3-h5 dtsi
> refactor, commit message change to met new arm64 naming scheme,
s/change to met/change to meet/ or s/change to met/changed to meet/ ?
> diff --git a/arch/arm64/boot/dts/allwinner/sunxi-h3-h5.dtsi b/arch/arm64/boot/dts/allwinner/sunxi-h3-h5.dtsi
> new file mode 120000
> index 000000000000..036f01dc2b9b
> --- /dev/null
> +++ b/arch/arm64/boot/dts/allwinner/sunxi-h3-h5.dtsi
> @@ -0,0 +1 @@
> +../../../../arm/boot/dts/sunxi-h3-h5.dtsi
> \ No newline at end of file
But it's missing more than just a newline, isn't it? Shouldn't it read
#include <../../../../arm/boot/dts/sunxi-h3-h5.dtsi>
?
--
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2017-02-26 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170226011956.53581-1-icenowy@aosc.xyz>
[not found] ` <20170226011956.53581-6-icenowy@aosc.xyz>
2017-02-26 3:46 ` [PATCH v5 5/7] arm: dts: sun8i: split Allwinner H3 .dtsi Chen-Yu Tsai
2017-02-27 8:20 ` Marc Zyngier
[not found] ` <20170226011956.53581-7-icenowy@aosc.xyz>
2017-02-26 8:55 ` Rask Ingemann Lambertsen [this message]
2017-02-26 9:00 ` [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi Chen-Yu Tsai
[not found] ` <20170226011956.53581-8-icenowy@aosc.xyz>
2017-02-26 9:19 ` [PATCH v5 7/7] arm64: dts: sunxi: add support for the Orange Pi PC 2 board Rask Ingemann Lambertsen
[not found] ` <20170226011956.53581-2-icenowy@aosc.xyz>
2017-02-27 8:25 ` [PATCH v5 1/7] arm64: allwinner: Kconfig: add essential pinctrl driver for H5 Maxime Ripard
[not found] ` <20170226011956.53581-3-icenowy@aosc.xyz>
2017-02-26 9:52 ` [PATCH v5 2/7] clk: sunxi-ng: rename sun8i-h3 driver to sunxi-h3-h5 Rask Ingemann Lambertsen
2017-02-27 12:24 ` Maxime Ripard
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=20170226085553.b6o6mv7ibe5op4dg@localhost \
--to=rask@formelder.dk \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
--cc=will.deacon@arm.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