From: Shawn Guo <shawnguo2@yeah.net>
To: Fabio Estevam <festevam@gmail.com>
Cc: Adam Ford <aford173@gmail.com>,
linux-arm-kernel@lists.infradead.org, aford@beaconembedded.com,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/2] arm64: dts: imx8mp-beacon-kit: Fix errors found from CHECK_DTBS
Date: Sun, 16 Jun 2024 15:01:45 +0800 [thread overview]
Message-ID: <Zm6N2W4E/DeHIMDQ@dragon> (raw)
In-Reply-To: <CAOMZO5CVrEEj20v+EDX7rmCvW29wL+gD37mfMZAp-uY=tnz-rQ@mail.gmail.com>
On Sat, Jun 01, 2024 at 02:43:07PM -0300, Fabio Estevam wrote:
> On Sat, Jun 1, 2024 at 10:52 AM Adam Ford <aford173@gmail.com> wrote:
>
> > adv_bridge: hdmi@3d {
> > compatible = "adi,adv7535";
> > - reg = <0x3d>, <0x3c>, <0x3e>, <0x3f>;
> > - reg-names = "main", "cec", "edid", "packet";
> > + reg = <0x3d>;
> > + reg-names = "main";
> > interrupt-parent = <&gpio4>;
> > interrupts = <27 IRQ_TYPE_EDGE_FALLING>;
> > adi,dsi-lanes = <4>;
> > #sound-dai-cells = <0>;
> > + avdd-supply = <&buck5>;
> > + dvdd-supply = <&buck5>;
> > + pvdd-supply = <&buck5>;
> > + a2vdd-supply = <&buck5>;
> > + v1p2-supply = <&buck5>;
> > + v3p3-supply = <&buck4>;
> > +
>
> The extra blank line is not needed.
Fixed it up and applied, thanks!
next prev parent reply other threads:[~2024-06-16 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 13:52 [PATCH V3 1/2] arm64: dts: imx8mp-beacon-kit: Enable ADV7535 Hot Plug Detect Adam Ford
2024-06-01 13:52 ` [PATCH V3 2/2] arm64: dts: imx8mp-beacon-kit: Fix errors found from CHECK_DTBS Adam Ford
2024-06-01 17:43 ` Fabio Estevam
2024-06-16 7:01 ` Shawn Guo [this message]
2024-06-01 17:41 ` [PATCH V3 1/2] arm64: dts: imx8mp-beacon-kit: Enable ADV7535 Hot Plug Detect Fabio Estevam
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=Zm6N2W4E/DeHIMDQ@dragon \
--to=shawnguo2@yeah.net \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).