From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: akpm@osdl.org, mingo@elte.hu, pj@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] sched: introduce child field in sched_domain
Date: Fri, 22 Sep 2006 19:52:59 +1000 [thread overview]
Message-ID: <4513B27B.5040602@yahoo.com.au> (raw)
In-Reply-To: <20060921143924.A25601@unix-os.sc.intel.com>
Siddha, Suresh B wrote:
> Andrew,
>
> Please drop sched-generic-sched_group-cpu-power-setup.patch in your
> -mm tree and add these two split up patches instead.
>
> First patch appended and second patch will follow this.
Thanks Suresh. These are both
Acked-by: Nick Piggin <npiggin@suse.de>
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-09-22 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 21:39 [patch 1/2] sched: introduce child field in sched_domain Siddha, Suresh B
2006-09-21 21:44 ` [patch 2/2] sched: cleanup sched_group cpu_power setup Siddha, Suresh B
2006-09-22 9:52 ` Nick Piggin [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=4513B27B.5040602@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox