From: Viresh Kumar <viresh.kumar@linaro.org>
To: mingo@redhat.com, peterz@infradead.org
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
linux-kernel@vger.kernel.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, arvind.chauhan@arm.com,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/3] sched: Sched Domains: Fixups
Date: Mon, 10 Jun 2013 16:27:17 +0530 [thread overview]
Message-ID: <cover.1370861520.git.viresh.kumar@linaro.org> (raw)
Peter/Ingo,
These are minor fixes that I could find for code responsible for creating sched
domains. They are rebased of my earlier fixes:
https://lkml.org/lkml/2013/6/4/253
I couldn't find them in linux-next or tip/master and so giving this link.
Viresh Kumar (3):
sched: don't initialize alloc_state in build_sched_domains
sched: don't sd->child to NULL when it is already NULL
sched: Create for_each_sd_topology()
kernel/sched/core.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
--
1.7.12.rc2.18.g61b472e
next reply other threads:[~2013-06-10 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 10:57 Viresh Kumar [this message]
2013-06-10 10:57 ` [PATCH 1/3] sched: don't initialize alloc_state in build_sched_domains Viresh Kumar
2013-06-19 18:40 ` [tip:sched/core] sched: Don' t initialize alloc_state in build_sched_domains() tip-bot for Viresh Kumar
2013-06-10 10:57 ` [PATCH 2/3] sched: don't sd->child to NULL when it is already NULL Viresh Kumar
2013-06-10 13:33 ` Viresh Kumar
2013-06-19 18:40 ` [tip:sched/core] sched: Don't set sd-> child " tip-bot for Viresh Kumar
2013-06-10 10:57 ` [PATCH 3/3] sched: Create for_each_sd_topology() Viresh Kumar
2013-06-19 18:40 ` [tip:sched/core] " tip-bot for Viresh Kumar
2013-06-18 10:00 ` [PATCH 0/3] sched: Sched Domains: Fixups Peter Zijlstra
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.1370861520.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=robin.randhawa@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.