From: "tip-bot2 for Hao Jia" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Hao Jia <jiahao.os@bytedance.com>, Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/urgent] sched/fair: Make update_entity_lag() static
Date: Tue, 29 Aug 2023 19:32:06 -0000 [thread overview]
Message-ID: <169333752613.27769.784028076271904268.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230829030325.69128-1-jiahao.os@bytedance.com>
The following commit has been merged into the sched/urgent branch of tip:
Commit-ID: c958ca2013e28e7573ad95c028198cb67c1352dd
Gitweb: https://git.kernel.org/tip/c958ca2013e28e7573ad95c028198cb67c1352dd
Author: Hao Jia <jiahao.os@bytedance.com>
AuthorDate: Tue, 29 Aug 2023 11:03:25 +08:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Tue, 29 Aug 2023 21:05:28 +02:00
sched/fair: Make update_entity_lag() static
The function update_entity_lag() is only used inside the kernel/sched/fair.c file.
Make it static.
Signed-off-by: Hao Jia <jiahao.os@bytedance.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20230829030325.69128-1-jiahao.os@bytedance.com
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 911d006..8dbff6e 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -699,7 +699,7 @@ u64 avg_vruntime(struct cfs_rq *cfs_rq)
*
* XXX could add max_slice to the augmented data to track this.
*/
-void update_entity_lag(struct cfs_rq *cfs_rq, struct sched_entity *se)
+static void update_entity_lag(struct cfs_rq *cfs_rq, struct sched_entity *se)
{
s64 lag, limit;
prev parent reply other threads:[~2023-08-29 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 3:03 [PATCH] " Hao Jia
2023-08-29 19:32 ` tip-bot2 for Hao Jia [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=169333752613.27769.784028076271904268.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=jiahao.os@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.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 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®