lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <TYCPR01MB112699830AA2FC0A8348D9818868CA@TYCPR01MB11269.jpnprd01.prod.outlook.com>
Date:   Thu, 14 Dec 2023 09:33:38 +0000
From:   Biju Das <biju.das.jz@...renesas.com>
To:     "Berg, Johannes" <johannes.berg@...el.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

Hi Johannes,

> -----Original Message-----
> From: Berg, Johannes <johannes.berg@...el.com>
> Sent: Thursday, December 14, 2023 9:32 AM
> 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.

Cool. Thanks for the pushfix.

Cheers,
Biju

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ