From: Peter Zijlstra <peterz@infradead.org>
To: "xiaofeng.yan" <xiaofeng.yan@huawei.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, xiaofeng_yan2004@126.com
Subject: Re: [PATCH] sched/rt: Fix a comment in struct sched_dl_entity
Date: Thu, 8 May 2014 13:04:22 +0200 [thread overview]
Message-ID: <20140508110422.GI2844@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <1399545080-17823-1-git-send-email-xiaofeng.yan@huawei.com>
On Thu, May 08, 2014 at 10:31:20AM +0000, xiaofeng.yan wrote:
> Change sched_setscheduler2() to sched_setscheduler() in the comments.
> There isn't function sched_setscheduler2() in the main line.
> The previous EDF version defines this function
> before being merged into the main line.
> User should use sched_setscheduler() instead of
> sched_setscheduler2() now.
Nah, you fail.. the interface is now called sched_setattr()
next prev parent reply other threads:[~2014-05-08 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 10:31 [PATCH] sched/rt: Fix a comment in struct sched_dl_entity xiaofeng.yan
2014-05-08 11:04 ` Peter Zijlstra [this message]
2014-05-09 3:33 ` xiaofeng.yan
-- strict thread matches above, loose matches on Subject: below --
2014-05-09 3:21 xiaofeng.yan
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=20140508110422.GI2844@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=xiaofeng.yan@huawei.com \
--cc=xiaofeng_yan2004@126.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