[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230518092939.2a2c8c40@canb.auug.org.au>
Date: Thu, 18 May 2023 09:29:39 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>
Cc: Jakub Kicinski <kuba@...nel.org>,
Dario Binacchi <dario.binacchi@...rulasolutions.com>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Simon Horman <horms@...ge.net.au>
Subject: Re: linux-next: build failure after merge of the net tree
Hi all,
On Thu, 18 May 2023 09:06:34 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the net tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> Error: arch/arm/boot/dts/stm32f746.dtsi:265.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
> make[2]: *** [scripts/Makefile.lib:419: arch/arm/boot/dts/stm32f746-disco.dtb] Error 1
> Error: arch/arm/boot/dts/stm32f746.dtsi:265.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
> make[2]: *** [scripts/Makefile.lib:419: arch/arm/boot/dts/stm32f769-disco.dtb] Error 1
> Error: arch/arm/boot/dts/stm32f746.dtsi:265.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
>
> Caused by commit
>
> 0920ccdf41e3 ("ARM: dts: stm32: add CAN support on stm32f746")
>
> I have used the net tree from next-20230517 for today.
This also meant that I used the ipvs tree from next-20230517 (because
it had merged the net tree).
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists