From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.19-stable 204/9999] kernel/sched/stubs.c:8:5: warning: no previous prototype for 'sched_isolate_cpu'
Date: Sat, 22 Jan 2022 07:58:54 +0800 [thread overview]
Message-ID: <202201220740.3itLwKmy-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Hi Quentin,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.19-stable
head: 90a691fca4c2525068d9908ac203e9f09e4e33c0
commit: eead51495c8760858c32d9ad0332ffc94397aa82 [204/9999] ANDROID: GKI: sched: stub sched_isolate symbols
config: x86_64-randconfig-a011 (https://download.01.org/0day-ci/archive/20220122/202201220740.3itLwKmy-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# 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
make 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 'sched_isolate_cpu' [-Wmissing-prototypes]
8 | int sched_isolate_cpu(int cpu)
| ^~~~~~~~~~~~~~~~~
>> kernel/sched/stubs.c:14:5: warning: no previous prototype for 'sched_unisolate_cpu_unlocked' [-Wmissing-prototypes]
14 | int sched_unisolate_cpu_unlocked(int cpu)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> kernel/sched/stubs.c:20:5: warning: no previous prototype for 'sched_unisolate_cpu' [-Wmissing-prototypes]
20 | int sched_unisolate_cpu(int cpu)
| ^~~~~~~~~~~~~~~~~~~
>> kernel/sched/stubs.c:26:5: warning: no previous prototype for 'set_task_boost' [-Wmissing-prototypes]
26 | int set_task_boost(int boost, u64 period)
| ^~~~~~~~~~~~~~
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(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Quentin Perret <qperret@google.com>
Cc: 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 204/9999] kernel/sched/stubs.c:8:5: warning: no previous prototype for 'sched_isolate_cpu'
Date: Sat, 22 Jan 2022 07:58:54 +0800 [thread overview]
Message-ID: <202201220740.3itLwKmy-lkp@intel.com> (raw)
Hi Quentin,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.19-stable
head: 90a691fca4c2525068d9908ac203e9f09e4e33c0
commit: eead51495c8760858c32d9ad0332ffc94397aa82 [204/9999] ANDROID: GKI: sched: stub sched_isolate symbols
config: x86_64-randconfig-a011 (https://download.01.org/0day-ci/archive/20220122/202201220740.3itLwKmy-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# 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
make 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 'sched_isolate_cpu' [-Wmissing-prototypes]
8 | int sched_isolate_cpu(int cpu)
| ^~~~~~~~~~~~~~~~~
>> kernel/sched/stubs.c:14:5: warning: no previous prototype for 'sched_unisolate_cpu_unlocked' [-Wmissing-prototypes]
14 | int sched_unisolate_cpu_unlocked(int cpu)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> kernel/sched/stubs.c:20:5: warning: no previous prototype for 'sched_unisolate_cpu' [-Wmissing-prototypes]
20 | int sched_unisolate_cpu(int cpu)
| ^~~~~~~~~~~~~~~~~~~
>> kernel/sched/stubs.c:26:5: warning: no previous prototype for 'set_task_boost' [-Wmissing-prototypes]
26 | int set_task_boost(int boost, u64 period)
| ^~~~~~~~~~~~~~
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
next reply other threads:[~2022-01-21 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 23:58 kernel test robot [this message]
2022-01-21 23:58 ` [ammarfaizi2-block:google/android/kernel/common/android-4.19-stable 204/9999] kernel/sched/stubs.c:8:5: warning: no previous prototype for 'sched_isolate_cpu' kernel test robot
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=202201220740.3itLwKmy-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.