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: [RFC PATCH] sched/fair: tg_set_cfs_slice() can be static
Date: Tue, 1 May 2018 08:29:56 +0800 [thread overview]
Message-ID: <20180501002956.GA22627@lkp-ne02> (raw)
In-Reply-To: <20180430192925.12589-1-xiyou.wangcong@gmail.com>
Fixes: 601aedfafd22 ("sched/fair: make CFS bandwidth slice per cpu group")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index abc48d9..daa1843 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6665,7 +6665,7 @@ long tg_get_cfs_period(struct task_group *tg)
return cfs_period_us;
}
-int tg_set_cfs_slice(struct task_group *tg, long cfs_slice_us)
+static int tg_set_cfs_slice(struct task_group *tg, long cfs_slice_us)
{
u64 quota, slice;
@@ -6683,7 +6683,7 @@ int tg_set_cfs_slice(struct task_group *tg, long cfs_slice_us)
return 0;
}
-long tg_get_cfs_slice(struct task_group *tg)
+static long tg_get_cfs_slice(struct task_group *tg)
{
u64 slice_us;
next prev parent reply other threads:[~2018-05-01 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 19:29 [PATCH] sched/fair: make CFS bandwidth slice per cpu group 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 ` kbuild test robot [this message]
2018-05-01 0:31 ` kbuild test robot
2018-05-01 0:57 ` kbuild test robot
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=20180501002956.GA22627@lkp-ne02 \
--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