From: 宋牧春 <songmuchun@bytedance.com>
To: mingo@kernel.org, peterz@infradead.org, juri.lelli@redhat.com,
Vincent Guittot <vincent.guittot@linaro.org>,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
Benjamin Segall <bsegall@google.com>,
mgorman@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: add __init to sched_init_granularity functions
Date: Mon, 13 Apr 2020 23:07:03 +0800 [thread overview]
Message-ID: <CAMZfGtUY_GLXZ4jV4s0UZqsVF0W57dzUh0wVGynXYCy3CMN4iA@mail.gmail.com> (raw)
In-Reply-To: <20200406074750.56533-1-songmuchun@bytedance.com>
On Mon, Apr 6, 2020 at 3:48 PM Muchun Song <songmuchun@bytedance.com> wrote:
>
> Function sched_init_granularity() is only called from __init
> functions, so mark it __init as well.
>
> Signed-off-by: Muchun Song <songmuchun@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 1141c7e77564d..6f05843c76d7d 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -191,7 +191,7 @@ static void update_sysctl(void)
> #undef SET_SYSCTL
> }
>
> -void sched_init_granularity(void)
> +void __init sched_init_granularity(void)
> {
> update_sysctl();
> }
> --
> 2.11.0
>
Ping guys. Any suggestions?
--
Yours,
Muchun
next prev parent reply other threads:[~2020-04-13 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 7:47 [PATCH] sched/fair: add __init to sched_init_granularity functions Muchun Song
2020-04-13 15:07 ` 宋牧春 [this message]
2020-04-13 15:44 ` Steven Rostedt
2020-05-01 18:22 ` [tip: sched/core] sched/fair: Mark sched_init_granularity __init tip-bot2 for Muchun Song
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=CAMZfGtUY_GLXZ4jV4s0UZqsVF0W57dzUh0wVGynXYCy3CMN4iA@mail.gmail.com \
--to=songmuchun@bytedance.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).