From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [tip:sched/core 23/23] kernel/sched/topology.c:17:2: error: 'sched_debug_verbose' undeclared; did you mean 'sched_debug_setup'?
Date: Sat, 17 Apr 2021 14:47:46 +0800 [thread overview]
Message-ID: <202104171441.AKFwtRfO-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3682 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head: a1b93fc0377e73dd54f819a993f83291324bb54a
commit: a1b93fc0377e73dd54f819a993f83291324bb54a [23/23] sched/debug: Rename the sched_debug parameter to sched_verbose
config: arc-randconfig-r003-20210416 (attached as .config)
compiler: arceb-elf-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=a1b93fc0377e73dd54f819a993f83291324bb54a
git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git fetch --no-tags tip sched/core
git checkout a1b93fc0377e73dd54f819a993f83291324bb54a
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=arc
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 >>):
kernel/sched/topology.c: In function 'sched_debug_setup':
>> kernel/sched/topology.c:17:2: error: 'sched_debug_verbose' undeclared (first use in this function); did you mean 'sched_debug_setup'?
17 | sched_debug_verbose = true;
| ^~~~~~~~~~~~~~~~~~~
| sched_debug_setup
kernel/sched/topology.c:17:2: note: each undeclared identifier is reported only once for each function it appears in
kernel/sched/topology.c: In function 'sched_debug':
kernel/sched/topology.c:25:9: error: 'sched_debug_verbose' undeclared (first use in this function); did you mean 'sched_debug_setup'?
25 | return sched_debug_verbose;
| ^~~~~~~~~~~~~~~~~~~
| sched_debug_setup
kernel/sched/topology.c: In function 'sched_domain_debug':
kernel/sched/topology.c:134:7: error: 'sched_debug_verbose' undeclared (first use in this function); did you mean 'sched_debug_setup'?
134 | if (!sched_debug_verbose)
| ^~~~~~~~~~~~~~~~~~~
| sched_debug_setup
kernel/sched/topology.c: In function 'build_sched_domains':
kernel/sched/topology.c:2144:12: error: 'sched_debug_verbose' undeclared (first use in this function); did you mean 'sched_debug_setup'?
2144 | if (rq && sched_debug_verbose) {
| ^~~~~~~~~~~~~~~~~~~
| sched_debug_setup
In file included from include/linux/perf_event.h:25,
from include/linux/trace_events.h:10,
from include/trace/syscall.h:7,
from include/linux/syscalls.h:85,
from kernel/sched/sched.h:66,
from kernel/sched/topology.c:5:
At top level:
arch/arc/include/asm/perf_event.h:126:23: warning: 'arc_pmu_cache_map' defined but not used [-Wunused-const-variable=]
126 | static const unsigned arc_pmu_cache_map[C(MAX)][C(OP_MAX)][C(RESULT_MAX)] = {
| ^~~~~~~~~~~~~~~~~
arch/arc/include/asm/perf_event.h:91:27: warning: 'arc_pmu_ev_hw_map' defined but not used [-Wunused-const-variable=]
91 | static const char * const arc_pmu_ev_hw_map[] = {
| ^~~~~~~~~~~~~~~~~
vim +17 kernel/sched/topology.c
14
15 static int __init sched_debug_setup(char *str)
16 {
> 17 sched_debug_verbose = true;
18
19 return 0;
20 }
21 early_param("sched_verbose", sched_debug_setup);
22
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32436 bytes --]
next reply other threads:[~2021-04-17 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 6:47 kernel test robot [this message]
2021-04-17 9:06 ` [tip:sched/core 23/23] kernel/sched/topology.c:17:2: error: 'sched_debug_verbose' undeclared; did you mean 'sched_debug_setup'? Borislav Petkov
2021-04-17 11:42 ` Peter Zijlstra
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=202104171441.AKFwtRfO-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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