[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM4PR11MB53594DB860C5FA1539FDC570E98CA@DM4PR11MB5359.namprd11.prod.outlook.com>
Date: Thu, 14 Dec 2023 09:31:58 +0000
From: "Berg, Johannes" <johannes.berg@...el.com>
To: Biju Das <biju.das.jz@...renesas.com>,
"naresh.kamboju@...aro.org" <naresh.kamboju@...aro.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
CC: "arnd@...db.de" <arnd@...db.de>,
"Berg, Benjamin" <benjamin.berg@...el.com>,
"dan.carpenter@...aro.org" <dan.carpenter@...aro.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"lkft-triage@...ts.linaro.org" <lkft-triage@...ts.linaro.org>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@...el.com>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Re: next: arm64: gcc-8-defconfig - failed -
net/wireless/shipped-certs.c:92:1: error: expected '}' before numeric
constant
>
> FYI, This issue is seen on today next as well, the generated code[2] is missing
> a comma leading to Build failure. Is it a requirement to use latest toolchain for
> linux-next?
Well, no surprise since I was out yesterday😉
The issue isn't the toolchain or anything - it's related to the ordering in which the two files are returned when make checks for them... I've pushed a fix.
johannes
--
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Powered by blists - more mailing lists