From: kernel test robot <lkp@intel.com>
To: Quentin Perret <qperret@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@gnuweeb.org>,
linux-kernel@vger.kernel.org,
Saravana Kannan <saravanak@google.com>
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.19-stable 201/9999] kernel/sched/stubs.c:8:5: warning: no previous prototype for function 'sched_isolate_cpu'
Date: Tue, 1 Feb 2022 21:15:15 +0800 [thread overview]
Message-ID: <202202012133.0supCHiV-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.19-stable
head: b45c5eeda8dea785e3d411380b486a209768f6b2
commit: eead51495c8760858c32d9ad0332ffc94397aa82 [201/9999] ANDROID: GKI: sched: stub sched_isolate symbols
config: x86_64-randconfig-r026-20220131 (https://download.01.org/0day-ci/archive/20220201/202202012133.0supCHiV-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 6b1e844b69f15bb7dffaf9365cd2b355d2eb7579)
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/eead51495c8760858c32d9ad0332ffc94397aa82
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android-4.19-stable
git checkout eead51495c8760858c32d9ad0332ffc94397aa82
# 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=x86_64 SHELL=/bin/bash drivers/nvmem/ kernel/sched/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/sched/stubs.c:8:5: warning: no previous prototype for function 'sched_isolate_cpu' [-Wmissing-prototypes]
int sched_isolate_cpu(int cpu)
^
kernel/sched/stubs.c:8:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int sched_isolate_cpu(int cpu)
^
static
>> kernel/sched/stubs.c:14:5: warning: no previous prototype for function 'sched_unisolate_cpu_unlocked' [-Wmissing-prototypes]
int sched_unisolate_cpu_unlocked(int cpu)
^
kernel/sched/stubs.c:14:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int sched_unisolate_cpu_unlocked(int cpu)
^
static
>> kernel/sched/stubs.c:20:5: warning: no previous prototype for function 'sched_unisolate_cpu' [-Wmissing-prototypes]
int sched_unisolate_cpu(int cpu)
^
kernel/sched/stubs.c:20:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int sched_unisolate_cpu(int cpu)
^
static
>> kernel/sched/stubs.c:26:5: warning: no previous prototype for function 'set_task_boost' [-Wmissing-prototypes]
int set_task_boost(int boost, u64 period)
^
kernel/sched/stubs.c:26:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int set_task_boost(int boost, u64 period)
^
static
4 warnings generated.
vim +/sched_isolate_cpu +8 kernel/sched/stubs.c
7
> 8 int sched_isolate_cpu(int cpu)
9 {
10 return -EINVAL;
11 }
12 EXPORT_SYMBOL_GPL(sched_isolate_cpu);
13
> 14 int sched_unisolate_cpu_unlocked(int cpu)
15 {
16 return -EINVAL;
17 }
18 EXPORT_SYMBOL_GPL(sched_unisolate_cpu_unlocked);
19
> 20 int sched_unisolate_cpu(int cpu)
21 {
22 return -EINVAL;
23 }
24 EXPORT_SYMBOL_GPL(sched_unisolate_cpu);
25
> 26 int set_task_boost(int boost, u64 period)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-01 13:15 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=202202012133.0supCHiV-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwml@gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=qperret@google.com \
--cc=saravanak@google.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