From: Neil Armstrong <narmstrong@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: meson: remove empty lines from aml-s905x-cc v2 dts
Date: Mon, 26 Oct 2020 16:08:11 +0100 [thread overview]
Message-ID: <1cf726fc-cd78-c2d4-ceee-fe099d550e9f@baylibre.com> (raw)
In-Reply-To: <20201026134101.10594-1-christianshewitt@gmail.com>
On 26/10/2020 14:41, Christian Hewitt wrote:
> Fixes: 63fafc5a046b ("arm64: dts: meson: initial support for aml-s905x-cc v2")
>
> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
> ---
> .../boot/dts/amlogic/meson-gxl-s905x-libretech-cc-v2.dts | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-libretech-cc-v2.dts b/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-libretech-cc-v2.dts
> index 675eaa87963e..9a3c08e6e6cc 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-libretech-cc-v2.dts
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-libretech-cc-v2.dts
> @@ -84,7 +84,6 @@
> regulator-always-on;
> };
>
> -
> vcck: regulator-vcck {
> compatible = "regulator-fixed";
> regulator-name = "VCCK";
> @@ -124,7 +123,6 @@
> regulator-always-on;
> };
>
> -
> vddio_card: regulator-vddio-card {
> compatible = "regulator-gpio";
> regulator-name = "VDDIO_CARD";
> @@ -195,7 +193,6 @@
> };
> };
>
> -
> &aiu {
> status = "okay";
> };
> @@ -207,7 +204,6 @@
> hdmi-phandle = <&hdmi_tx>;
> };
>
> -
> ðmac {
> status = "okay";
> };
>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
next prev parent reply other threads:[~2020-10-26 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 13:41 [PATCH] arm64: dts: meson: remove empty lines from aml-s905x-cc v2 dts Christian Hewitt
2020-10-26 15:08 ` Neil Armstrong [this message]
2020-11-05 19:32 ` Kevin Hilman
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=1cf726fc-cd78-c2d4-ceee-fe099d550e9f@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).