linux-kernel - Re: linux-next: build failure after merge of the imx-mxs 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <87cab9ba-883b-4275-8170-12b525399751@app.fastmail.com>
Date:   Mon, 31 Oct 2022 08:11:57 +1000
From:   Alistair <alistair@...stair23.me>
To:     "Stephen Rothwell" <sfr@...b.auug.org.au>,
        "Shawn Guo" <shawnguo@...nel.org>
Cc:     "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
        "Linux Next Mailing List" <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the imx-mxs tree

On Mon, 31 Oct 2022, at 8:09 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/imx7d-remarkable2.dts:26.15-44.5: ERROR (phandle_references): /thermal-zones/epd-thermal: Reference to non-existent node or label "epd_pmic"
> 
> ERROR: Input tree has errors, aborting (use -f to force output)

Sorry, that's completely my fault. Apparently I had a local change
that didn't get committed. I'll send a new version of this patch.

Alistair

> 
> Caused by commit
> 
>   b725fda78895 ("ARM: dts: imx7d-remarkable2: Enable silergy,sy7636a")
> 
> I have used the imx-mxs tree from next-20221028 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell
>