From: kbuild test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: [tip:WIP.sched/core 6/9] kernel//sched/core.c:2299:6: warning: no previous prototype for function 'send_call_function_single_ipi'
Date: Thu, 28 May 2020 03:09:44 +0800 [thread overview]
Message-ID: <202005280340.WP1u4gQJ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.sched/core
head: 68a1740c687d4a75b9e9dea0ab0aae61f167c880
commit: 516bf252eeb5d316895d83a5bcbe9d5668c5d41c [6/9] smp: Optimize send_call_function_single_ipi()
config: x86_64-randconfig-a015-20200527 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 3393cc4cebf9969db94dc424b7a2b6195589c33b)
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 x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git checkout 516bf252eeb5d316895d83a5bcbe9d5668c5d41c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
kernel//sched/core.c:2116:6: warning: no previous prototype for function 'sched_set_stop_task' [-Wmissing-prototypes]
void sched_set_stop_task(int cpu, struct task_struct *stop)
^
kernel//sched/core.c:2116:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void sched_set_stop_task(int cpu, struct task_struct *stop)
^
static
>> kernel//sched/core.c:2299:6: warning: no previous prototype for function 'send_call_function_single_ipi' [-Wmissing-prototypes]
void send_call_function_single_ipi(int cpu)
^
kernel//sched/core.c:2299:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void send_call_function_single_ipi(int cpu)
^
static
kernel//sched/core.c:806:28: warning: unused function 'uclamp_bucket_base_value' [-Wunused-function]
static inline unsigned int uclamp_bucket_base_value(unsigned int clamp_value)
^
kernel//sched/core.c:1045:1: warning: unused function 'uclamp_update_active' [-Wunused-function]
uclamp_update_active(struct task_struct *p, enum uclamp_id clamp_id)
^
4 warnings generated.
vim +/send_call_function_single_ipi +2299 kernel//sched/core.c
2298
> 2299 void send_call_function_single_ipi(int cpu)
2300 {
2301 struct rq *rq = cpu_rq(cpu);
2302
2303 if (!set_nr_if_polling(rq->idle))
2304 arch_send_call_function_single_ipi(cpu);
2305 else
2306 trace_sched_wake_idle_without_ipi(cpu);
2307 }
2308
---
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: 29807 bytes --]
reply other threads:[~2020-05-27 19:32 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=202005280340.WP1u4gQJ%lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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
all inboxes | Powered by JetHome®