On 2023-01-18 08:37, Mark Brown wrote:
On Fri, Jan 06, 2023 at 07:24:19PM +0000, Mark Brown wrote:
The KVM rseq test is failing to build in -next due to a commit merged from the tip tree which adds a wrapper for sys_getcpu() to the rseq kselftests, conflicting with the wrapper already included in the KVM selftest:
Any thoughts on this? The KVM tests are still failing to build in -next:
I'm OK with the fix you submitted in this email thread. Should it be routed through -tip ?
Acked-by: Mathieu Desnoyers mathieu.desnoyers@efficios.com
Thanks,
Mathieu
rseq_test.c:48:13: error: conflicting types for ‘sys_getcpu’ 48 | static void sys_getcpu(unsigned *cpu) | ^~~~~~~~~~ In file included from rseq_test.c:23: ../rseq/rseq.c:82:12: note: previous definition of ‘sys_getcpu’ was here 82 | static int sys_getcpu(unsigned *cpu, unsigned *node) | ^~~~~~~~~~
https://storage.kernelci.org/next/master/next-20230118/arm64/defconfig/gcc-1...