From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Douglas Anderson <dianders@chromium.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-nonmm-unstable 54/56] kernel/watchdog.c:526:36: error: too many arguments to function call, expected 0, have 1
Date: Sat, 5 Aug 2023 10:00:33 -0700 [thread overview]
Message-ID: <20230805100033.37f1df3bf720a7c21ad8980d@linux-foundation.org> (raw)
In-Reply-To: <202308051236.R7HDiE39-lkp@intel.com>
On Sat, 5 Aug 2023 12:30:30 +0800 kernel test robot <lkp@intel.com> wrote:
> >> kernel/watchdog.c:526:36: error: too many arguments to function call, expected 0, have 1
> trigger_allbutcpu_cpu_backtrace(smp_processor_id());
Thanks, I did this:
--- a/include/linux/nmi.h~nmi_backtrace-allow-excluding-an-arbitrary-cpu-fix
+++ a/include/linux/nmi.h
@@ -190,7 +190,7 @@ static inline bool trigger_all_cpu_backt
{
return false;
}
-static inline bool trigger_allbutcpu_cpu_backtrace(void)
+static inline bool trigger_allbutcpu_cpu_backtrace(int exclude_cpu)
{
return false;
}
_
prev parent reply other threads:[~2023-08-05 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 4:30 kernel test robot
2023-08-05 17:00 ` Andrew Morton [this message]
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=20230805100033.37f1df3bf720a7c21ad8980d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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