From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [vincent.guittot:sched/pelt 4/5] kernel/sched/sched.h:706:27: error: 'struct sched_entity' has no member named 'my_q'
Date: Fri, 07 Feb 2020 23:14:53 +0800 [thread overview]
Message-ID: <202002072341.nDdG7X99%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
tree: https://git.linaro.org/people/vincent.guittot/kernel.git sched/pelt
head: 72c9cba7acfa9d51fe5ced5ff3a3cde60c69e022
commit: 26d3f5b799e5a4ee66ed32186e4684a1af702b36 [4/5] sched/fair: replace runnable load average by runnable average
config: mips-nlm_xlp_defconfig (attached as .config)
compiler: mips64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 26d3f5b799e5a4ee66ed32186e4684a1af702b36
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from kernel/sched/core.c:9:0:
kernel/sched/sched.h: In function 'se_update_runnable':
>> kernel/sched/sched.h:706:27: error: 'struct sched_entity' has no member named 'my_q'
se->runnable_weight = se->my_q->h_nr_running;
^~
vim +706 kernel/sched/sched.h
702
703 static inline void se_update_runnable(struct sched_entity *se)
704 {
705 if (!entity_is_task(se)) {
> 706 se->runnable_weight = se->my_q->h_nr_running;
707 }
708 }
709
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 21333 bytes --]
reply other threads:[~2020-02-07 15:14 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=202002072341.nDdG7X99%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.