From: tip-bot for Rakib Mullick <rakib.mullick@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
rakib.mullick@gmail.com, peterz@infradead.org,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:sched/core] sched: Use bool type for rq->idle_at_tick
Date: Sat, 30 Apr 2011 07:16:01 GMT [thread overview]
Message-ID: <tip-eea502ffd4aeef233b5eadbde405a9df92d57a5e@git.kernel.org> (raw)
In-Reply-To: <1304100062.19359.6.camel@localhost.localdomain>
Commit-ID: eea502ffd4aeef233b5eadbde405a9df92d57a5e
Gitweb: http://git.kernel.org/tip/eea502ffd4aeef233b5eadbde405a9df92d57a5e
Author: Rakib Mullick <rakib.mullick@gmail.com>
AuthorDate: Sat, 30 Apr 2011 00:01:02 +0600
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sat, 30 Apr 2011 00:17:14 +0200
sched: Use bool type for rq->idle_at_tick
Searching over the scheduler code for uses of rq->idle_at_tick
shows us that it's used for making TRUE/FALSE decision.
Still its type is 'unsigned char' so using 'bool' would be
cleaner.
Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1304100062.19359.6.camel@localhost.localdomain
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index f11a2a5..a492209 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -505,7 +505,7 @@ struct rq {
unsigned long cpu_power;
- unsigned char idle_at_tick;
+ bool idle_at_tick;
/* For active balancing */
int post_schedule;
int active_balance;
next prev parent reply other threads:[~2011-04-30 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 18:01 [PATCH] sched: Use proper type for runqueue's idle_at_tick Rakib Mullick
2011-04-30 7:16 ` tip-bot for Rakib Mullick [this message]
2011-05-11 11:08 ` [tip:sched/core] sched: Use bool type for rq->idle_at_tick Peter Zijlstra
2011-05-11 11:19 ` Ingo Molnar
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=tip-eea502ffd4aeef233b5eadbde405a9df92d57a5e@git.kernel.org \
--to=rakib.mullick@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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