From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Michal Hocko <mhocko@suse.com>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Petr Mladek <pmladek@suse.com>,
Pingfan Liu <kernelfans@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: next: arm: kernel/watchdog.c:521:36: error: too many arguments to function call, expected 0, have 1
Date: Mon, 7 Aug 2023 14:12:03 +0530 [thread overview]
Message-ID: <CA+G9fYsnoxm82ik3YNs_qUdZkxkNmVrknhC+ezqSKrEx6WxJ7g@mail.gmail.com> (raw)
[ 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 <lkft@linaro.org>
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
next reply other threads:[~2023-08-07 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 8:42 Naresh Kamboju [this message]
2023-08-07 8:50 ` next: arm: kernel/watchdog.c:521:36: error: too many arguments to function call, expected 0, have 1 Arnd Bergmann
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=CA+G9fYsnoxm82ik3YNs_qUdZkxkNmVrknhC+ezqSKrEx6WxJ7g@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=kernelfans@gmail.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mhocko@suse.com \
--cc=pmladek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).