From: "tip-bot2 for YueHaibing" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: YueHaibing <yuehaibing@huawei.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched: Remove unused inline function __rq_clock_broken()
Date: Tue, 05 Oct 2021 14:12:05 -0000 [thread overview]
Message-ID: <163344312520.25758.13885264891205156672.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210914095244.52780-1-yuehaibing@huawei.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 32ed980c3020b7a19e26dc488c10817807ba2a41
Gitweb: https://git.kernel.org/tip/32ed980c3020b7a19e26dc488c10817807ba2a41
Author: YueHaibing <yuehaibing@huawei.com>
AuthorDate: Tue, 14 Sep 2021 17:52:44 +08:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Tue, 05 Oct 2021 15:51:55 +02:00
sched: Remove unused inline function __rq_clock_broken()
These is no caller in tree since commit
523e979d3164 ("sched/core: Use PELT for scale_rt_capacity()")
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20210914095244.52780-1-yuehaibing@huawei.com
---
kernel/sched/sched.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
index 8712fc4..198058b 100644
--- a/kernel/sched/sched.h
+++ b/kernel/sched/sched.h
@@ -1426,11 +1426,6 @@ static inline struct cfs_rq *group_cfs_rq(struct sched_entity *grp)
extern void update_rq_clock(struct rq *rq);
-static inline u64 __rq_clock_broken(struct rq *rq)
-{
- return READ_ONCE(rq->clock);
-}
-
/*
* rq::clock_update_flags bits
*
prev parent reply other threads:[~2021-10-05 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 9:52 [PATCH -next] sched: Remove unused inline function __rq_clock_broken() YueHaibing
2021-09-16 11:59 ` [tip: sched/core] " tip-bot2 for YueHaibing
2021-09-17 18:37 ` tip-bot2 for YueHaibing
2021-10-05 14:12 ` tip-bot2 for YueHaibing [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=163344312520.25758.13885264891205156672.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).