linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Mon, 31 Oct 2022 08:11:57 +1000	[thread overview]
Message-ID: <87cab9ba-883b-4275-8170-12b525399751@app.fastmail.com> (raw)
In-Reply-To: <20221031090904.7ce6ca3c@canb.auug.org.au>

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
> 

  reply	other threads:[~2022-10-30 22:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 22:09 linux-next: build failure after merge of the imx-mxs tree Stephen Rothwell
2022-10-30 22:11 ` Alistair [this message]
2022-10-31  0:52   ` Shawn Guo
  -- strict thread matches above, loose matches on Subject: below --
2023-03-07  1:31 Stephen Rothwell
2021-12-06 22:10 Stephen Rothwell
2021-12-07  7:27 ` Michal Vokáč
2020-11-03  1:00 Stephen Rothwell
2020-11-03  6:39 ` Shawn Guo
2020-02-18  2:08 Stephen Rothwell
2020-02-18  2:18 ` Peng Fan
2020-02-18  9:38   ` Shawn Guo
2019-12-11 21:35 Stephen Rothwell
2019-12-12  1:33 ` Shawn Guo
2019-12-12  9:45   ` Lucas Stach
2019-12-12 11:37     ` Shawn Guo
2019-05-20 22:37 Stephen Rothwell
2019-05-21  2:16 ` Anson Huang
2019-05-21  4:43   ` Shawn Guo
2019-04-22 22:45 Stephen Rothwell
2019-04-22 22:54 ` Fabio Estevam
2019-04-23  2:12 ` Shawn Guo
2019-01-10 22:30 Stephen Rothwell
2019-01-10 22:56 ` Stephen Rothwell
2019-01-10 23:15   ` Lukasz Majewski
2019-01-12  1:23     ` Shawn Guo
2015-06-01 12:35 Stephen Rothwell
2015-05-29 11:28 Stephen Rothwell
2015-05-29 13:16 ` Shawn Guo

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=87cab9ba-883b-4275-8170-12b525399751@app.fastmail.com \
    --to=alistair@alistair23.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).