[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <502ee081-8e09-422a-a1f9-be40aeaa84fb@app.fastmail.com>
Date: Mon, 29 Jul 2024 11:54:47 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Geert Uytterhoeven" <geert@...ux-m68k.org>, linux-kernel@...r.kernel.org
Cc: "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
linux-mips@...r.kernel.org, dm-devel@...ts.linux.dev,
linuxppc-dev@...ts.ozlabs.org, linux-btrfs@...r.kernel.org,
intel-xe@...ts.freedesktop.org, linux-sh@...r.kernel.org,
sparclinux@...r.kernel.org, linux-hexagon@...r.kernel.org,
linux-sh@...r.kernel.org
Subject: Re: Build regressions/improvements in v6.11-rc1
On Mon, Jul 29, 2024, at 11:35, Geert Uytterhoeven wrote:
>
>> + /kisskb/src/kernel/fork.c: error: #warning clone3() entry point is missing, please fix [-Werror=cpp]: => 3072:2
>
> sh4-gcc13/se{7619,7750}_defconfig
> sh4-gcc13/sh-all{mod,no,yes}config
> sh4-gcc13/sh-defconfig
> sparc64-gcc5/sparc-allnoconfig
> sparc64-gcc{5,13}/sparc32_defconfig
> sparc64-gcc{5,13}/sparc64-{allno,def}config
> sparc64-gcc13/sparc-all{mod,no}config
> sparc64-gcc13/sparc64-allmodconfig
Hexagon and NIOS2 as well, but this is expected. I really just
moved the warning into the actual implementation, the warning
is the same as before. hexagon and sh look like they should be
trivial, it's just that nobody seems to care. I'm sure the
patches were posted before and never applied.
sparc and nios2 do need some real work to write and test
the wrappers.
It does look like CONFIG_WERROR did not fail the build before
505d66d1abfb ("clone3: drop __ARCH_WANT_SYS_CLONE3 macro")
as it probably was intended.
Arnd
Powered by blists - more mailing lists