From: kbuild test robot <lkp@intel.com>
To: Muchun Song <smuchun@gmail.com>
Cc: kbuild-all@01.org, mingo@kernel.org, peterz@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/rt: Remove unnecessary CONFIG_RT_GROUP_SCHED in rt_se_prio()
Date: Tue, 30 Oct 2018 23:13:09 +0800 [thread overview]
Message-ID: <201810302302.5Bvf0Uf8%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181030144530.89995-1-smuchun@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
Hi Muchun,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.19 next-20181030]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Muchun-Song/sched-rt-Remove-unnecessary-CONFIG_RT_GROUP_SCHED-in-rt_se_prio/20181030-225925
config: i386-randconfig-x002-201843 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/sched/rt.c: In function 'rt_se_prio':
>> kernel/sched/rt.c:900:15: error: 'struct rt_rq' has no member named 'highest_prio'
return rt_rq->highest_prio.curr;
^~
vim +900 kernel/sched/rt.c
ac086bc2 kernel/sched_rt.c Peter Zijlstra 2008-04-19 894
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 895 static inline int rt_se_prio(struct sched_rt_entity *rt_se)
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 896 {
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 897 struct rt_rq *rt_rq = group_rt_rq(rt_se);
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 898
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 899 if (rt_rq)
e864c499 kernel/sched_rt.c Gregory Haskins 2008-12-29 @900 return rt_rq->highest_prio.curr;
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 901
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 902 return rt_task_of(rt_se)->prio;
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 903 }
6f505b16 kernel/sched_rt.c Peter Zijlstra 2008-01-25 904
:::::: The code at line 900 was first introduced by commit
:::::: e864c499d9e57805ae1f9e7ea404dd223759cd53 sched: track the next-highest priority on each runqueue
:::::: TO: Gregory Haskins <ghaskins@novell.com>
:::::: CC: Gregory Haskins <ghaskins@novell.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31105 bytes --]
next prev parent reply other threads:[~2018-10-30 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 14:45 Muchun Song
2018-10-30 15:13 ` kbuild test robot [this message]
2018-10-30 15:42 ` 宋牧春
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=201810302302.5Bvf0Uf8%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=smuchun@gmail.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
all inboxes | Powered by JetHome®