Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: ifd214418:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-1087-g968661d8e1-fm-20221021.001-g968661d8
Mime-Version: 1.0
Message-Id: <87cab9ba-883b-4275-8170-12b525399751@app.fastmail.com>
In-Reply-To: <20221031090904.7ce6ca3c@canb.auug.org.au>
References: <20221031090904.7ce6ca3c@canb.auug.org.au>
Date:   Mon, 31 Oct 2022 08:11:57 +1000
From:   Alistair <alistair@alistair23.me>
To:     "Stephen Rothwell" <sfr@canb.auug.org.au>,
        "Shawn Guo" <shawnguo@kernel.org>
Cc:     "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
        "Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the imx-mxs tree
Content-Type: text/plain
Precedence: bulk

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
>