From: kernel test robot <lkp@intel.com>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: [ammarfaizi2-block:palmer/linux/fixes 6/6] arch/riscv/kernel/cpu-hotplug.c:43:9: error: implicit declaration of function 'numa_remove_cpu'; did you mean 'remove_cpu'?
Date: Wed, 9 Feb 2022 15:04:27 +0800 [thread overview]
Message-ID: <202202091500.dMNAJXAU-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block palmer/linux/fixes
head: c3c94752087e789419be7024116c0a7b22883541
commit: c3c94752087e789419be7024116c0a7b22883541 [6/6] riscv: cpu-hotplug: clear cpu from numa map when teardown
config: riscv-randconfig-r042-20220209 (https://download.01.org/0day-ci/archive/20220209/202202091500.dMNAJXAU-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/ammarfaizi2/linux-block/commit/c3c94752087e789419be7024116c0a7b22883541
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block palmer/linux/fixes
git checkout c3c94752087e789419be7024116c0a7b22883541
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash arch/riscv/kernel/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/riscv/kernel/cpu-hotplug.c: In function '__cpu_disable':
>> arch/riscv/kernel/cpu-hotplug.c:43:9: error: implicit declaration of function 'numa_remove_cpu'; did you mean 'remove_cpu'? [-Werror=implicit-function-declaration]
43 | numa_remove_cpu(cpu);
| ^~~~~~~~~~~~~~~
| remove_cpu
cc1: some warnings being treated as errors
vim +43 arch/riscv/kernel/cpu-hotplug.c
24
25 /*
26 * __cpu_disable runs on the processor to be shutdown.
27 */
28 int __cpu_disable(void)
29 {
30 int ret = 0;
31 unsigned int cpu = smp_processor_id();
32
33 if (!cpu_ops[cpu] || !cpu_ops[cpu]->cpu_stop)
34 return -EOPNOTSUPP;
35
36 if (cpu_ops[cpu]->cpu_disable)
37 ret = cpu_ops[cpu]->cpu_disable(cpu);
38
39 if (ret)
40 return ret;
41
42 remove_cpu_topology(cpu);
> 43 numa_remove_cpu(cpu);
44 set_cpu_online(cpu, false);
45 irq_migrate_all_off_this_cpu();
46
47 return ret;
48 }
49
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-09 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202202091500.dMNAJXAU-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.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
all inboxes | Powered by JetHome®