* Re: Build regressions/improvements in v6.11-rc1 [not found] ` <bd4e9928-17b3-9257-8ba7-6b7f9bbb639a@linux-m68k.org> @ 2024-07-29 9:54 ` Arnd Bergmann 2024-07-29 10:07 ` Geert Uytterhoeven 0 siblings, 1 reply; 2+ messages in thread From: Arnd Bergmann @ 2024-07-29 9:54 UTC (permalink / raw) To: Geert Uytterhoeven, linux-kernel Cc: Greg Kroah-Hartman, linux-mips, dm-devel, linuxppc-dev, linux-btrfs, intel-xe, linux-sh, sparclinux, linux-hexagon, linux-sh 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Build regressions/improvements in v6.11-rc1 2024-07-29 9:54 ` Build regressions/improvements in v6.11-rc1 Arnd Bergmann @ 2024-07-29 10:07 ` Geert Uytterhoeven 0 siblings, 0 replies; 2+ messages in thread From: Geert Uytterhoeven @ 2024-07-29 10:07 UTC (permalink / raw) To: Arnd Bergmann Cc: linux-kernel, Greg Kroah-Hartman, linux-mips, dm-devel, linuxppc-dev, linux-btrfs, intel-xe, linux-sh, sparclinux, linux-hexagon Hi Arnd, On Mon, Jul 29, 2024 at 11:55 AM Arnd Bergmann <arnd@arndb.de> wrote: > 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. Indeed. The actual regression is that this turned into a fatal error with -Werror. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-07-29 10:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAHk-=wiyNokz0d3b=GRORij=mGvwoYHy=+bv6m2Hu_VqNdg66g@mail.gmail.com>
[not found] ` <20240729092807.2235937-1-geert@linux-m68k.org>
[not found] ` <bd4e9928-17b3-9257-8ba7-6b7f9bbb639a@linux-m68k.org>
2024-07-29 9:54 ` Build regressions/improvements in v6.11-rc1 Arnd Bergmann
2024-07-29 10:07 ` Geert Uytterhoeven
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).