From: KernelCI bot <bot@kernelci•org>
To: kernelci-results@groups•io
Cc: regressions@lists•linux.dev, gus@collabora•com,
linux-next@vger•kernel.org
Subject: [REGRESSION] next/master: (build) initialization of ‘int (*)(void *)’ from incompatible pointer type...
Date: Wed, 17 Dec 2025 04:59:03 -0000 [thread overview]
Message-ID: <176594754327.3108.9546235188357594114@77bfb67944a2> (raw)
Hello,
New build issue found on next/master:
---
initialization of ‘int (*)(void *)’ from incompatible pointer type ‘int (*)(void)’ [-Wincompatible-pointer-types] in drivers/irqchip/irq-riscv-aplic-main.o (drivers/irqchip/irq-riscv-aplic-main.c) [logspec:kbuild,kbuild.compiler.error]
---
- dashboard: https://d.kernelci.org/i/maestro:c537d0d22aa608b88bb407d6e02b6a733d3f78cf
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 12b95d29eb979e5c4f4f31bb05817bc935c52050
- tags: next-20251217
Please include the KernelCI tag when submitting a fix:
Reported-by: kernelci.org bot <bot@kernelci•org>
Log excerpt:
=====================================================
drivers/irqchip/irq-riscv-aplic-main.c:111:20: error: initialization of ‘int (*)(void *)’ from incompatible pointer type ‘int (*)(void)’ [-Wincompatible-pointer-types]
111 | .suspend = aplic_syscore_suspend,
| ^~~~~~~~~~~~~~~~~~~~~
drivers/irqchip/irq-riscv-aplic-main.c:111:20: note: (near initialization for ‘aplic_syscore_ops.suspend’)
drivers/irqchip/irq-riscv-aplic-main.c:112:19: error: initialization of ‘void (*)(void *)’ from incompatible pointer type ‘void (*)(void)’ [-Wincompatible-pointer-types]
112 | .resume = aplic_syscore_resume,
| ^~~~~~~~~~~~~~~~~~~~
drivers/irqchip/irq-riscv-aplic-main.c:112:19: note: (near initialization for ‘aplic_syscore_ops.resume’)
drivers/irqchip/irq-riscv-aplic-main.c: In function ‘aplic_probe’:
drivers/irqchip/irq-riscv-aplic-main.c:375:17: error: implicit declaration of function ‘register_syscore_ops’; did you mean ‘register_syscore’? [-Wimplicit-function-declaration]
375 | register_syscore_ops(&aplic_syscore_ops);
| ^~~~~~~~~~~~~~~~~~~~
| register_syscore
=====================================================
# Builds where the incident occurred:
## defconfig on (riscv):
- compiler: gcc-14
- config: https://files.kernelci.org/kbuild-gcc-14-riscv-build-only-69422a0bcbfd84c3cdbdaaa0/.config
- dashboard: https://d.kernelci.org/build/maestro:69422a0bcbfd84c3cdbdaaa0
#kernelci issue maestro:c537d0d22aa608b88bb407d6e02b6a733d3f78cf
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists•linux.dev
Made with love by the KernelCI team - https://kernelci.org
next reply other threads:[~2025-12-17 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 4:59 KernelCI bot [this message]
2025-12-17 5:43 ` [REGRESSION] next/master: (build) initialization of ‘int (*)(void *)’ from incompatible pointer type Stephen Rothwell
2025-12-17 17:31 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2025-12-17 4:59 KernelCI bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176594754327.3108.9546235188357594114@77bfb67944a2 \
--to=bot@kernelci$(echo .)org \
--cc=gus@collabora$(echo .)com \
--cc=kernelci-results@groups$(echo .)io \
--cc=kernelci@lists$(echo .)linux.dev \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=regressions@lists$(echo .)linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox