2023-08-07 09:04:22

by Naresh Kamboju

[permalink] [raw]
Subject: next: arm: kernel/watchdog.c:521:36: error: too many arguments to function call, expected 0, have 1

[ resending in plain text mode. sorry ]

While building arm mxs_defconfig with gcc-12 and clang-16 on
Linux next-20230807 tag the following build regression was found.

Reported-by: Linux Kernel Functional Testing <[email protected]>

Build log:
--------
kernel/watchdog.c:521:36: error: too many arguments to function call,
expected 0, have 1
trigger_allbutcpu_cpu_backtrace(smp_processor_id());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~
include/linux/smp.h:271:29: note: expanded from macro 'smp_processor_id'
# define smp_processor_id() __smp_processor_id()
^~~~~~~~~~~~~~~~~~~~
include/linux/smp.h:264:31: note: expanded from macro '__smp_processor_id'
#define __smp_processor_id(x) raw_smp_processor_id(x)
^~~~~~~~~~~~~~~~~~~~~~~
include/linux/smp.h:198:34: note: expanded from macro 'raw_smp_processor_id'
#define raw_smp_processor_id() 0
^
include/linux/nmi.h:193:20: note: 'trigger_allbutcpu_cpu_backtrace'
declared here
static inline bool trigger_allbutcpu_cpu_backtrace(void)
^
1 error generated.
make[4]: *** [scripts/Makefile.build:243: kernel/watchdog.o] Error 1



Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230807/testrun/18858575/suite/build/test/clang-16-mxs_defconfig/log
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230807/testrun/18858575/suite/build/test/clang-16-mxs_defconfig/history/

--
Linaro LKFT
https://lkft.linaro.org


2023-08-07 10:29:08

by Arnd Bergmann

[permalink] [raw]
Subject: Re: next: arm: kernel/watchdog.c:521:36: error: too many arguments to function call, expected 0, have 1

On Mon, Aug 7, 2023, at 10:42, Naresh Kamboju wrote:
> [ resending in plain text mode. sorry ]
>
> While building arm mxs_defconfig with gcc-12 and clang-16 on
> Linux next-20230807 tag the following build regression was found.
>
> Reported-by: Linux Kernel Functional Testing <[email protected]>
>

I sent a patch when I saw this today, and Andrew already had
the same fix.

Arnd