From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [peterz-queue:sched/scx 39/42] kernel/sched/sched.h:2371:45: error: too many arguments to function call, expected 2, have 3
Date: Sun, 28 Jul 2024 06:42:22 +0800 [thread overview]
Message-ID: <202407280602.enrMgVrF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/scx
head: df64e1ce653e6748aff3f6d7dea17a02c7905075
commit: 4dc9ef89e52432135c71303203f5b9868f2dde6c [39/42] sched: Combine the last put_prev_task() and the first set_next_task()
config: x86_64-randconfig-001-20240725 (https://download.01.org/0day-ci/archive/20240728/202407280602.enrMgVrF-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240728/202407280602.enrMgVrF-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/202407280602.enrMgVrF-lkp@intel.com/
Note: the peterz-queue/sched/scx HEAD df64e1ce653e6748aff3f6d7dea17a02c7905075 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
In file included from kernel/sched/core.c:88:
>> kernel/sched/sched.h:2371:45: error: too many arguments to function call, expected 2, have 3
2371 | prev->sched_class->put_prev_task(rq, prev, false);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~
1 error generated.
vim +2371 kernel/sched/sched.h
2367
2368 static inline void put_prev_task(struct rq *rq, struct task_struct *prev)
2369 {
2370 WARN_ON_ONCE(rq->curr != prev);
> 2371 prev->sched_class->put_prev_task(rq, prev, false);
2372 }
2373
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-27 22:42 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=202407280602.enrMgVrF-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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