[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <74bc4baa-96df-f41d-2838-c18be52a5051@ysoft.com>
Date: Tue, 7 Dec 2021 08:27:00 +0100
From: Michal Vokáč <michal.vokac@...ft.com>
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 06. 12. 21 23:10, Stephen Rothwell wrote:
> 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.
>
Hi Stephen,
I already send a patch for this yesterday short time after
the kernel test robot reported the same failure. It is on
the devicetree mailing list:
https://www.spinics.net/lists/devicetree/msg461729.html
Sorry for my mistake though,
Michal
Powered by blists - more mailing lists