From: "Heiko Stübner" <heiko@sntech.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>, arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/2] Rockchip dts64 updates for 5.1
Date: Fri, 15 Feb 2019 20:32:01 +0100 [thread overview]
Message-ID: <3976614.8kaIahWTG7@diego> (raw)
In-Reply-To: <CAK8P3a2UkmVOJDddi3rC=GFcBSeqciNuYaT8s3i5E4bOwJE1Bg@mail.gmail.com>
Am Freitag, 15. Februar 2019, 16:38:43 CET schrieb Arnd Bergmann:
> On Fri, Feb 15, 2019 at 2:45 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Fri, Feb 1, 2019 at 12:24 PM Heiko Stuebner <heiko@sntech.de> wrote:
> > > New boards are the Rock Pi 4, NanoPC-T4 and NanoPi-M4, with the last
> > > two being part of a family and sharing bigger parts of the devicetree.
> > > rk3328 got sound-related upgrades and a wider patch drops mmc display-wp
> > > fields from nodes which shouldn't use it.
> >
> > Pulled into arm/dt, nice to see the additional rk3399 boards. Thanks,
>
> I still get some warnings during 'make dtb', all specific to rk3399:
>
> ../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'
> ../arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts:46.9-50.5:
> Warning (graph_port): /edp-panel/ports: graph port node name should be
> 'port'
> ../arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dts:94.9-98.5:
> Warning (graph_port): /edp-panel/ports: graph port node name should be
> 'port'
>
> Can you see what is going on and send a fix?
hmm, that should actually be fixed by the fixes-pull requests, see
https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git/commit/?h=arm/fixes&id=26cd8657c7e745686a4c54a5cccf721ede208a25
for reference, which supposedly fixes exactly these issues.
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-15 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 11:23 [GIT PULL 1/2] Rockchip dts32 updates for 5.1 Heiko Stuebner
2019-02-01 11:24 ` [GIT PULL 2/2] Rockchip dts64 " Heiko Stuebner
2019-02-15 13:45 ` Arnd Bergmann
2019-02-15 15:38 ` Arnd Bergmann
2019-02-15 19:32 ` Heiko Stübner [this message]
2019-02-15 19:52 ` Arnd Bergmann
2019-02-15 13:36 ` [GIT PULL 1/2] Rockchip dts32 " Arnd Bergmann
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=3976614.8kaIahWTG7@diego \
--to=heiko@sntech.de \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@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