linux-kernel - Re: linux-next: build failure after merge of the qcom tree

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] [day] [month] [year] [list]

Message-ID: <20190423235041.GF112750@google.com>
Date:   Tue, 23 Apr 2019 16:50:41 -0700
From:   Matthias Kaehlcke <mka@...omium.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Andy Gross <andy.gross@...aro.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Douglas Anderson <dianders@...omium.org>,
        Stephen Boyd <swboyd@...omium.org>
Subject: Re: linux-next: build failure after merge of the qcom tree

On Wed, Apr 24, 2019 at 09:25:31AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the qcom tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/qcom-apq8064.dtsi:1297.29-1309.5: ERROR (phandle_references): /soc/dsi-phy@...0200: Reference to non-existent node or label "xo_board"
> 
> Caused by commit
> 
>   3560af5a56b5 ("ARM: dts: qcom-apq8064: Set 'xo_board' as ref clock of the DSI PHY")
> 
> I have used the version of the qcom tree from next-20190423 for today.

I thought I built-tested this, but probably only did arm64 builds :(

I'm working on a fix.

Matthias