From: kernel test robot <lkp@intel.com>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: [linux-next:pending-fixes 265/356] arch/riscv/kernel/cpu-hotplug.c:43:2: error: implicit declaration of function 'numa_remove_cpu'
Date: Thu, 10 Feb 2022 16:51:31 +0800 [thread overview]
Message-ID: <202202101650.4mU4Ubis-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
head: dfd7907f4e4fe53417c1436f4a727a143e0ba2d2
commit: c3c94752087e789419be7024116c0a7b22883541 [265/356] riscv: cpu-hotplug: clear cpu from numa map when teardown
config: riscv-randconfig-c006-20220210 (https://download.01.org/0day-ci/archive/20220210/202202101650.4mU4Ubis-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project aa845d7a245d85c441d0bd44fc7b6c3be8f3de8d)
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
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c3c94752087e789419be7024116c0a7b22883541
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next pending-fixes
git checkout c3c94752087e789419be7024116c0a7b22883541
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash
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:43:2: error: implicit declaration of function 'numa_remove_cpu' [-Werror,-Wimplicit-function-declaration]
numa_remove_cpu(cpu);
^
arch/riscv/kernel/cpu-hotplug.c:43:2: note: did you mean 'remove_cpu'?
include/linux/cpu.h:128:5: note: 'remove_cpu' declared here
int remove_cpu(unsigned int cpu);
^
1 error generated.
vim +/numa_remove_cpu +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-10 8:51 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=202202101650.4mU4Ubis-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kernelfans@gmail.com \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).