Greg,
Kernel CI is reporting a build failure on v6.6-rt:
https://grafana.kernelci.org/d/build/build?orgId=1&var-datasource=defaul...
It's in arch/riscv/kernel/cpufeature.c where a return statement in check_unaligned_access() doesn't have a value (and check_unaligned_access returns int).
Is 6.6 stable supporting RiscV? If so then we either have to fix that return, or backport the refactor of arch/riscv/kernel/cpufeature.c (f413aae96cda0). If it's not then who should I talk to about turning off riscv CI builds for v6.6-rt?
Thanks, Clark
On Fri, Aug 02, 2024 at 08:46:55PM +0000, Clark Williams wrote:
Greg,
Kernel CI is reporting a build failure on v6.6-rt:
https://grafana.kernelci.org/d/build/build?orgId=1&var-datasource=defaul...
It's in arch/riscv/kernel/cpufeature.c where a return statement in check_unaligned_access() doesn't have a value (and check_unaligned_access returns int).
Is 6.6 stable supporting RiscV? If so then we either have to fix that return, or backport the refactor of arch/riscv/kernel/cpufeature.c (f413aae96cda0). If it's not then who should I talk to about turning off riscv CI builds for v6.6-rt?
Why not ask the people responsible for the -rt patchset? If this isn't an issue on a non-rt kernel, then I think you found the problem :)
thanks,
greg k-h
On 2024-08-03 08:20:16 [+0200], Kroah-Hartman, Greg wrote:
On Fri, Aug 02, 2024 at 08:46:55PM +0000, Clark Williams wrote:
Greg,
Kernel CI is reporting a build failure on v6.6-rt:
https://grafana.kernelci.org/d/build/build?orgId=1&var-datasource=defaul...
It's in arch/riscv/kernel/cpufeature.c where a return statement in check_unaligned_access() doesn't have a value (and check_unaligned_access returns int).
Is 6.6 stable supporting RiscV? If so then we either have to fix that return, or backport the refactor of arch/riscv/kernel/cpufeature.c (f413aae96cda0). If it's not then who should I talk to about turning off riscv CI builds for v6.6-rt?
Why not ask the people responsible for the -rt patchset? If this isn't an issue on a non-rt kernel, then I think you found the problem :)
I'm sorry. I misunderstood Clark and assumed this is a stable issue. Now that I have the needed pointers, it is a RT-stable issue only. I'm going to drop the stable folks from Cc: and reply with a patch.
thanks,
greg k-h
Sebastian
linux-stable-mirror@lists.linaro.org