public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
	mingo@elte.hu, dmitry.adamushko@gmail.com,
	torvalds@linux-foundation.org, pj@sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]	cpu	hotplug,	sched:Introduce	cpu_active_map	and	redoscheddomainmanagment (take	2)
Date: Tue, 22 Jul 2008 10:45:45 -0400	[thread overview]
Message-ID: <4885F299.4090300@novell.com> (raw)
In-Reply-To: <1216736764.7257.99.camel@twins>

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

Peter Zijlstra wrote:
> On Tue, 2008-07-22 at 10:17 -0400, Gregory Haskins wrote:
>
>   
>> Thanks Peter.
>>
>> BTW: I should mention that this was just an RFC.  I haven't even build 
>> tested it yet.  I will do this now.
>>     
>
> Heh, might make sense to ensure it indeed builds before stuffing it into
> -tip ;-)
>
>   

Ok, it passes the sniff test without any corrections.  :)

Change the status from RFC to consider-for-inclusion.

-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2008-07-22 14:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 11:43 [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redo sched domain managment (take 2) Max Krasnyansky
2008-07-15 11:49 ` Marcel Holtmann
2008-07-15 11:52   ` Peter Zijlstra
2008-07-15 11:57     ` Marcel Holtmann
2008-07-15 12:03       ` Peter Zijlstra
2008-07-15 15:24       ` Linus Torvalds
2008-07-15 12:45 ` Gregory Haskins
2008-07-15 15:22 ` Linus Torvalds
2008-07-16  8:57 ` Dmitry Adamushko
2008-07-16 20:29   ` Max Krasnyansky
2008-07-16 21:55     ` Dmitry Adamushko
2008-07-16 12:12 ` Gregory Haskins
2008-07-16 21:44   ` Max Krasnyansky
2008-07-17  2:51     ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redosched " Gregory Haskins
2008-07-17  7:16       ` Max Krasnyansky
2008-07-17 11:57         ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redoscheddomain " Gregory Haskins
2008-07-17 18:52           ` Max Krasnyansky
2008-07-17 19:46             ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redoscheddomainmanagment " Gregory Haskins
2008-07-18 11:53               ` Peter Zijlstra
2008-07-18 12:22                 ` [PATCH] cpu hotplug, sched:Introduce " Gregory Haskins
2008-07-22  5:10                   ` Max Krasnyansky
2008-07-22 14:06                     ` Gregory Haskins
2008-07-22 14:16                       ` Peter Zijlstra
2008-07-22 14:17                         ` Gregory Haskins
2008-07-22 14:26                           ` Peter Zijlstra
2008-07-22 14:45                             ` Gregory Haskins [this message]
2008-07-22 19:32                       ` Max Krasnyansky
2008-08-11 13:11                       ` Gregory Haskins
2008-08-11 21:57                         ` Max Krasnyansky
2008-07-18 11:30 ` [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redo sched domain managment " 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=4885F299.4090300@novell.com \
    --to=ghaskins@novell.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=mingo@elte.hu \
    --cc=pj@sgi.com \
    --cc=torvalds@linux-foundation.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