linux-kernel - Re: [GIT PULL] arm64: dts: uniphier: UniPhier DT updates (64bit) for v4.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a3oKP-5hgZ+zBZGBgHV8YdCnKpif8-nArsKqVydsajWxw@mail.gmail.com>
Date:   Mon, 30 Oct 2017 14:24:23 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     arm-soc <arm@...nel.org>, Olof Johansson <olof@...om.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL] arm64: dts: uniphier: UniPhier DT updates (64bit) for v4.15

On Mon, Oct 23, 2017 at 7:40 PM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:

> UniPhier ARM64 SoC DT updates for v4.15
>
> - add thermal monitor and thermal zone nodes
> - add efuse nodes
> - fix W=2 warnings
> - add GPIO controller nodes and related properties
> - add resets properties

I noticed too late that your "ARM32 SoC DT" branch broke ARM64 (I
don't normally test
architectures that are not touched by a new branch. What happened here
is that commit
2bef7ca3798f ("ARM: dts: uniphier: route on-board device IRQ to GPIO
controller")
added a reference to the non-existing "gpio" label, causing a build error:

arch/arm64/boot/dts/socionext/uniphier-ld11-ref.dtb: ERROR
(phandle_references): Reference to non-existent node or label "gpio"

Since merging the ARM64 branch fixes the problem, I decided it's not
worth the trouble
of reverting the original merge, but please be careful to avoid build
problems like this
in the future.

The changes otherwise look all good, so I've pulled this into next/dt as well.

Thanks,

        Arnd