From: Heiko Stuebner <heiko@sntech.de>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vicente Bergas <vicencb@gmail.com>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
kernel@collabora.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: fix rk3300-gru-bob graph_port warning
Date: Sun, 27 Jan 2019 22:08:00 +0100 [thread overview]
Message-ID: <4055651.A8C7SXy0L7@phil> (raw)
In-Reply-To: <20190126103730.3883-1-enric.balletbo@collabora.com>
Am Samstag, 26. Januar 2019, 11:37:28 CET schrieb Enric Balletbo i Serra:
> Ports are described by child 'port' nodes contained in the device node.
> 'ports' is optional and is used to group all 'port' nodes which is not
> the case here.
>
> This patch fixes the following warning:
>
> arch/arm64/boot/dts/rockchip/rk3399-gru-bob.dts:25.9-29.5: Warning (graph_port): /edp-panel/ports: graph port node name should be 'port'
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
I've squashed all 3 into one and applied the result as fix for 5.0
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-27 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 10:37 [PATCH 1/3] arm64: dts: rockchip: fix rk3300-gru-bob graph_port warning Enric Balletbo i Serra
2019-01-26 10:37 ` [PATCH 2/3] arm64: dts: rockchip: fix rk3399-gru-kevin " Enric Balletbo i Serra
2019-01-26 10:37 ` [PATCH 3/3] arm64: dts: rockchip: fix rk3399-sapphire-excavator " Enric Balletbo i Serra
2019-01-27 21:08 ` Heiko Stuebner [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=4055651.A8C7SXy0L7@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vicencb@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;
as well as URLs for NNTP newsgroup(s).