From: YueHaibing <yuehaibing@huawei.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: <mingo@redhat.com>, <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 -next] sched/core: Make some functions static
Date: Thu, 18 Apr 2019 22:26:18 +0800 [thread overview]
Message-ID: <5f7e511a-bd78-e442-1252-2e46c0224960@huawei.com> (raw)
In-Reply-To: <20190418134031.GA59073@gmail.com>
On 2019/4/18 21:40, Ingo Molnar wrote:
>
> * Yue Haibing <yuehaibing@huawei.com> wrote:
>
>> From: YueHaibing <yuehaibing@huawei.com>
>>
>> Fix sparse warnings:
>>
>> kernel/sched/core.c:6524:11: warning: symbol 'min_cfs_quota_period' was not declared. Should it be static?
>> kernel/sched/core.c:6604:5: warning: symbol 'tg_set_cfs_quota' was not declared. Should it be static?
>> kernel/sched/core.c:6617:6: warning: symbol 'tg_get_cfs_quota' was not declared. Should it be static?
>> kernel/sched/core.c:6630:5: warning: symbol 'tg_set_cfs_period' was not declared. Should it be static?
>> kernel/sched/core.c:6640:6: warning: symbol 'tg_get_cfs_period' was not declared. Should it be static?
>>
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>
> Could you please also use the updated commit message I edited for v1,
> instead of just reverting to the old one?
Sorry, I do not notice that, fix it now.
>
> Thanks,
>
> Ingo
>
>
next prev parent reply other threads:[~2019-04-18 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 14:31 [PATCH " Yue Haibing
2019-04-18 12:25 ` [tip:sched/core] " tip-bot for YueHaibing
2019-04-18 12:48 ` Ingo Molnar
2019-04-18 13:17 ` YueHaibing
2019-04-18 13:29 ` [PATCH v2 -next] " Yue Haibing
2019-04-18 13:40 ` Ingo Molnar
2019-04-18 14:26 ` YueHaibing [this message]
2019-04-18 14:47 ` [PATCH v3 " Yue Haibing
2019-04-18 18:31 ` [tip:sched/core] " tip-bot for YueHaibing
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=5f7e511a-bd78-e442-1252-2e46c0224960@huawei.com \
--to=yuehaibing@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
Powered by JetHome