mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: mingo@elte.hu, dmitry.adamushko@gmail.com,
	a.p.zijlstra@chello.nl, torvalds@linux-foundation.org,
	pj@sgi.com, ghaskins@novell.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpu hotplug, sched: Introduce cpu_active_map and redo sched domain managment (take 2)
Date: Tue, 15 Jul 2008 13:49:37 +0200	[thread overview]
Message-ID: <1216122577.27242.57.camel@violet.holtmann.net> (raw)
In-Reply-To: <1216122229-4865-1-git-send-email-maxk@qualcomm.com>

Hi Max,

>   *  #ifdef CONFIG_HOTPLUG_CPU
>   *     cpu_possible_map - has bit 'cpu' set iff cpu is populatable
>   *     cpu_present_map  - has bit 'cpu' set iff cpu is populated
>   *     cpu_online_map   - has bit 'cpu' set iff cpu available to scheduler
> + *     cpu_active_map   - has bit 'cpu' set iff cpu available to migration

why not just fixing all spelling mistakes instead of keeping them
around ;)

Regards

Marcel



  reply	other threads:[~2008-07-15 11:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 11:43 Max Krasnyansky
2008-07-15 11:49 ` Marcel Holtmann [this message]
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
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=1216122577.27242.57.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dmitry.adamushko@gmail.com \
    --cc=ghaskins@novell.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

Powered by JetHome