From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: raistlin@linux.it, juri.lelli@gmail.com,
clark.williams@gmail.com, peterz@infradead.org, mingo@redhat.com,
namhyung@kernel.org, Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Subject: [PATCH 0/3 V2] sched: Collect the bits about priority into a new header file, include/linux/sched/prio.h.
Date: Mon, 10 Feb 2014 17:05:43 +0800 [thread overview]
Message-ID: <cover.1392022452.git.yangds.fnst@cn.fujitsu.com> (raw)
Hi Peter,
This patchset is version 2 about priority of sched. Please help to review.
Sorry for the late update about it, coming back from vacation.
v2:
* leave the task_prio() in kernel/sched/core.c
* remove macro TASK_NICE and implement it as static inline
function in include/linux/sched.h.
* remove #ifndef when include prio.h.
Dongsheng Yang (3):
sched: Move the priority specific bits into a new header file.
sched: Expose some macros related with priority.
sched: Implement task_nice as static inline function.
include/linux/sched.h | 12 +++++++++++-
include/linux/sched/prio.h | 40 ++++++++++++++++++++++++++++++++++++++++
include/linux/sched/rt.h | 19 +------------------
kernel/sched/core.c | 26 +++++++-------------------
kernel/sched/cputime.c | 4 ++--
kernel/sched/sched.h | 18 ------------------
6 files changed, 61 insertions(+), 58 deletions(-)
create mode 100644 include/linux/sched/prio.h
--
1.8.2.1
next reply other threads:[~2014-02-10 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 9:05 Dongsheng Yang [this message]
2014-02-10 9:05 ` [PATCH 1/3] sched: Move the priority specific bits into a new header file Dongsheng Yang
2014-02-10 9:05 ` [PATCH 2/3] sched: Expose some macros related with priority Dongsheng Yang
2014-02-10 9:05 ` [PATCH 3/3] sched: Implement task_nice as static inline function Dongsheng Yang
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=cover.1392022452.git.yangds.fnst@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=clark.williams@gmail.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
/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