From: tip-bot for Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
kamalesh@linux.vnet.ibm.com, a.p.zijlstra@chello.nl,
tglx@linutronix.de
Subject: [tip:sched/urgent] sched: Remove NULL assignment of dattr_cur
Date: Wed, 30 May 2012 06:43:12 -0700 [thread overview]
Message-ID: <tip-6a4c96eef42f835734a82c6b512abf9881b7c55d@git.kernel.org> (raw)
In-Reply-To: <20120523091411.GG5005@linux.vnet.ibm.com>
Commit-ID: 6a4c96eef42f835734a82c6b512abf9881b7c55d
Gitweb: http://git.kernel.org/tip/6a4c96eef42f835734a82c6b512abf9881b7c55d
Author: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
AuthorDate: Wed, 23 May 2012 14:44:11 +0530
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 30 May 2012 14:02:27 +0200
sched: Remove NULL assignment of dattr_cur
Remove explicit NULL assignment of static pointer
dattr_cur from init_sched_domains().
Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/20120523091411.GG5005@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/core.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 94d598a..c46958e 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6726,7 +6726,6 @@ static int init_sched_domains(const struct cpumask *cpu_map)
if (!doms_cur)
doms_cur = &fallback_doms;
cpumask_andnot(doms_cur[0], cpu_map, cpu_isolated_map);
- dattr_cur = NULL;
err = build_sched_domains(doms_cur[0], NULL);
register_sched_domain_sysctl();
prev parent reply other threads:[~2012-05-30 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 6:41 [PATCH] Trivial sched: Pass domain_attr to build_sched_domains() Kamalesh Babulal
2012-05-23 7:48 ` Peter Zijlstra
2012-05-23 9:14 ` Kamalesh Babulal
2012-05-30 13:43 ` tip-bot for Kamalesh Babulal [this message]
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-6a4c96eef42f835734a82c6b512abf9881b7c55d@git.kernel.org \
--to=kamalesh@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome