public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: r8a7795: Drop bogus HDMI node names suffixes
Date: Wed, 30 Aug 2017 13:10:58 +0300	[thread overview]
Message-ID: <3276171.anaVMsVBRO@avalon> (raw)
In-Reply-To: <1504087397-6211-1-git-send-email-geert+renesas@glider.be>

Hi Geert,

Thank you for the patch.

On Wednesday, 30 August 2017 13:03:17 EEST Geert Uytterhoeven wrote:
> Node names should not use numerical suffixes if the nodes can be
> distinguished by unit-address.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  arch/arm64/boot/dts/renesas/r8a7795.dtsi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> b/arch/arm64/boot/dts/renesas/r8a7795.dtsi index
> 8b4dbce860001224..e1ced54d11322cb4 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> @@ -2702,7 +2702,7 @@
>  			renesas,fcp = <&fcpf1>;
>  		};
> 
> -		hdmi0: hdmi0 at fead0000 {
> +		hdmi0: hdmi at fead0000 {
>  			compatible = "renesas,r8a7795-hdmi", "renesas,rcar-gen3-hdmi";
>  			reg = <0 0xfead0000 0 0x10000>;
>  			interrupts = <GIC_SPI 389 IRQ_TYPE_LEVEL_HIGH>;
> @@ -2727,7 +2727,7 @@
>  			};
>  		};
> 
> -		hdmi1: hdmi1 at feae0000 {
> +		hdmi1: hdmi at feae0000 {
>  			compatible = "renesas,r8a7795-hdmi", "renesas,rcar-gen3-hdmi";
>  			reg = <0 0xfeae0000 0 0x10000>;
>  			interrupts = <GIC_SPI 436 IRQ_TYPE_LEVEL_HIGH>;


-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2017-08-30 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 10:03 [PATCH] arm64: dts: r8a7795: Drop bogus HDMI node names suffixes Geert Uytterhoeven
2017-08-30 10:10 ` Laurent Pinchart [this message]
2017-08-31  8:36   ` Simon Horman

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=3276171.anaVMsVBRO@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.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