public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Shawn Guo <shawnguo@kernel•org>
Cc: "Michal Vokáč" <michal.vokac@ysoft•com>,
	"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
	"Linux Next Mailing List" <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the imx-mxs tree
Date: Tue, 7 Dec 2021 09:10:14 +1100	[thread overview]
Message-ID: <20211207091014.06063422@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

Error: arch/arm/boot/dts/imx6q-yapp4-crux.dts:24.1-7 Label or path codec not found
Error: arch/arm/boot/dts/imx6q-yapp4-crux.dts:52.1-7 Label or path sound not found
FATAL ERROR: Syntax error parsing input tree
Error: arch/arm/boot/dts/imx6qp-yapp4-crux-plus.dts:24.1-7 Label or path codec not found 
Error: arch/arm/boot/dts/imx6qp-yapp4-crux-plus.dts:52.1-7 Label or path sound not found 
FATAL ERROR: Syntax error parsing input tree

Caused by commit

  a4d744ac2bab ("ARM: dts: imx6dl-yapp4: Add Y Soft IOTA Crux/Crux+ board")

I have used the imx-mxs tree from next-20211206 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2021-12-06 22:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 22:10 Stephen Rothwell [this message]
2021-12-07  7:27 ` linux-next: build failure after merge of the imx-mxs tree Michal Vokáč
  -- strict thread matches above, loose matches on Subject: below --
2026-06-02 14:53 Mark Brown
2026-06-02 19:52 ` Frank Li
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
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=20211207091014.06063422@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=michal.vokac@ysoft$(echo .)com \
    --cc=shawnguo@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox