I had sent the only patch in patch form but I gather you prefer a pull request so sendign thsi instead. I verified and indeed I had quite a bit of 0-day build successes with this branch. The issue reported by 0-day came late with an sparc64 allyesconfig build. The issue were not found earlier with 0-day allyes config on a few other archs. I'll see I can get more build converage on modules for modules-next so we can catch random builds / gcc combos these earlier. The following changes since commit 348551ddaf311c76b01cdcbaf61b6fef06a49144: Merge tag 'pinctrl-v6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl (2023-05-02 15:40:41 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/ tags/modules-6.4-rc1-v2 for you to fetch changes up to 0b891c83d8c54cb70e186456c2191adb5fd98c56: module: include internal.h in module/dups.c (2023-05-02 20:33:36 -0700) ---------------------------------------------------------------- modules-6.4-rc1 v2 There is only one fix by Arnd far for modules pending which came in after the first pull request. The issue was found as part of some late compile tests with 0-day. I take it 0-day does some secondary late builds with after some initial ones. ---------------------------------------------------------------- Arnd Bergmann (1): module: include internal.h in module/dups.c kernel/module/dups.c | 2 ++ 1 file changed, 2 insertions(+)