From: Frank Li <Frank.li@nxp.com>
To: Mark Brown <broonie@kernel.org>
Cc: Alice Guo <alice.guo@nxp.com>,
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: Tue, 2 Jun 2026 15:52:01 -0400 [thread overview]
Message-ID: <ah80YTF1Df2_qcyK@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <ah7uaEyP7mLUYLqf@sirena.org.uk>
On Tue, Jun 02, 2026 at 03:53:28PM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the imx-mxs tree, today's linux-next build
> (arm_multi_v7_defconfig.log /tmp/next/x86_64 allmodconfig) failed
> like this:
>
> Error: /tmp/next/build/arch/arm/boot/dts/nxp/imx/imx7ulp.dtsi:337.14-15 syntax error
> FATAL ERROR: Unable to parse input tree
>
> Caused by commit
>
> 3d016a3272010 (arm64: dts: freescale: add ULP watchdog nodes for i.MX platforms)
>
> That's not a ;. I have used the version from next-20260601 instead.
Sorry, I just fixed it. It was caused by "arm64" tag actually touch "ARM"'s
code. I have not found it during applying patch and missed test ARM build
for this branch.
Frank
next prev parent reply other threads:[~2026-06-02 19:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 14:53 Mark Brown
2026-06-02 19:52 ` Frank Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-07 1:31 Stephen Rothwell
2022-10-30 22:09 Stephen Rothwell
2022-10-30 22:11 ` Alistair
2022-10-31 0:52 ` Shawn Guo
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=ah80YTF1Df2_qcyK@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alice.guo@nxp.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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
all inboxes | Powered by JetHome®