From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] Trivial sched: Pass domain_attr to build_sched_domains()
Date: Wed, 23 May 2012 14:44:11 +0530 [thread overview]
Message-ID: <20120523091411.GG5005@linux.vnet.ibm.com> (raw)
In-Reply-To: <1337759338.9698.45.camel@twins>
* Peter Zijlstra <peterz@infradead.org> [2012-05-23 09:48:58]:
> On Wed, 2012-05-23 at 12:11 +0530, Kamalesh Babulal wrote:
> > sched: Pass domain_attr to build_sched_domains()
> >
> > build_sched_domains() is called from init_sched_domains()
> > by explicitly passing NULL as second argument, which is
> > of type sched_domain_attr. This patch calls build_sched_domains()
> > with dattr_cur instead of NULL, as dattr_cur is also NULL.
>
> So what's the point? Rather clean up the dattr crap, no?
Thanks for the review.
As suggested, this version of patch drops dattr_cur from
init_sched_domains().
sched: Remove NULL assignment to 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>
---
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 22a19ae..964bf9d 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6734,7 +6734,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();
next prev parent reply other threads:[~2012-05-23 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 6:41 Kamalesh Babulal
2012-05-23 7:48 ` Peter Zijlstra
2012-05-23 9:14 ` Kamalesh Babulal [this message]
2012-05-30 13:43 ` [tip:sched/urgent] sched: Remove NULL assignment of dattr_cur tip-bot for Kamalesh Babulal
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=20120523091411.GG5005@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.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