From: kbuild test robot <lkp@intel.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Cong Wang <xiyou.wangcong@gmail.com>,
Paul Turner <pjt@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] sched/fair: make CFS bandwidth slice per cpu group
Date: Tue, 1 May 2018 08:57:32 +0800 [thread overview]
Message-ID: <201805010750.OF79lm3y%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180430192925.12589-1-xiyou.wangcong@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Hi Cong,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.17-rc3 next-20180430]
[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/Cong-Wang/sched-fair-make-CFS-bandwidth-slice-per-cpu-group/20180501-064013
config: i386-randconfig-x003-201817 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from kernel/sched/debug.c:12:0:
kernel/sched/sched.h: In function 'sched_default_cfs_bandwidth_slice':
>> kernel/sched/sched.h:438:14: error: 'sysctl_sched_cfs_bandwidth_slice' undeclared (first use in this function); did you mean 'sched_default_cfs_bandwidth_slice'?
return (u64)sysctl_sched_cfs_bandwidth_slice * NSEC_PER_USEC;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sched_default_cfs_bandwidth_slice
kernel/sched/sched.h:438:14: note: each undeclared identifier is reported only once for each function it appears in
vim +438 kernel/sched/sched.h
435
436 static inline u64 sched_default_cfs_bandwidth_slice(void)
437 {
> 438 return (u64)sysctl_sched_cfs_bandwidth_slice * NSEC_PER_USEC;
439 }
440
---
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: 26030 bytes --]
prev parent reply other threads:[~2018-05-01 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 19:29 Cong Wang
2018-04-30 19:42 ` Peter Zijlstra
2018-04-30 20:37 ` Cong Wang
2018-05-01 7:11 ` Peter Zijlstra
2018-05-01 18:06 ` Cong Wang
2018-05-01 0:29 ` kbuild test robot
2018-05-01 0:29 ` [RFC PATCH] sched/fair: tg_set_cfs_slice() can be static kbuild test robot
2018-05-01 0:31 ` [PATCH] sched/fair: make CFS bandwidth slice per cpu group kbuild test robot
2018-05-01 0:57 ` kbuild test robot [this message]
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=201805010750.OF79lm3y%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=efault@gmx.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=xiyou.wangcong@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®