[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdW1Cz_JJsTmssVz_0wjX_1_EEXGOvGjygPxTkcMsbR6Lw@mail.gmail.com>
Date: Mon, 3 Aug 2020 22:33:59 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
lkft-triage@...ts.linaro.org, stable <stable@...r.kernel.org>
Subject: Re: [PATCH 5.7 000/120] 5.7.13-rc1 review
Hi Greg,
On Mon, Aug 3, 2020 at 7:35 PM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Mon, Aug 03, 2020 at 08:58:20AM -0700, Guenter Roeck wrote:
> > On Mon, Aug 03, 2020 at 02:17:38PM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.7.13 release. There
> > > are 120 patches in this series, all will be posted as a response to this one.
> > > If anyone has any issues with these being applied, please let me know.
> > >
> > > Responses should be made by Wed, 05 Aug 2020 12:18:33 +0000. Anything
> > > received after that time might be too late.
> > >
> >
> > Building sparc64:allmodconfig ... failed
> > --------------
> > Error log:
> > <stdin>:1511:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> > In file included from arch/sparc/include/asm/percpu_64.h:11,
> > from arch/sparc/include/asm/percpu.h:5,
> > from include/linux/random.h:14,
> > from fs/crypto/policy.c:13:
> > arch/sparc/include/asm/trap_block.h:54:39: error: 'NR_CPUS' undeclared here (not in a function)
> > 54 | extern struct trap_per_cpu trap_block[NR_CPUS];
> >
> > Inherited from mainline. Builds are not complete yet;
> > we may see a few more failures (powerpc:ppc64e_defconfig
> > fails to build in mainline as well).
>
> If it gets fixed upstream, I'll fix it here :)
And else you'll release a known-broken v5.7.13?
Perhaps backporting should be a bit less aggressive?
This breakage was introduced in between v5.8-rc7 and v5.8, and backported
before people had the time to properly look into the v5.8 build bot logs.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists