From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android-4.19-stable 11009/30000] kernel/sched/stubs.c:8:5: warning: no previous prototype for function 'sched_isolate_cpu'
Date: Thu, 12 Dec 2024 19:36:33 +0800 [thread overview]
Message-ID: <202412121906.nSQrei7t-lkp@intel.com> (raw)
Hi Quentin,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android-4.19-stable
head: a8bf86a0e0fa05070897a210d706d5c4d83c26ac
commit: eead51495c8760858c32d9ad0332ffc94397aa82 [11009/30000] ANDROID: GKI: sched: stub sched_isolate symbols
config: x86_64-buildonly-randconfig-004-20241212 (https://download.01.org/0day-ci/archive/20241212/202412121906.nSQrei7t-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241212/202412121906.nSQrei7t-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412121906.nSQrei7t-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]
8 | 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
8 | 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]
14 | 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
14 | 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]
20 | 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
20 | int sched_unisolate_cpu(int cpu)
| ^
| static
>> kernel/sched/stubs.c:26:5: warning: no previous prototype for function 'set_task_boost' [-Wmissing-prototypes]
26 | 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
26 | 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
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-12 11:40 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=202412121906.nSQrei7t-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.