From: Christian Robottom Reis <kiko@linaro.org>
To: Mike Turquette <mturquette@ti.com>
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, linaro-dev@lists.linaro.org,
patches@linaro.org
Subject: Re: [PATCH 1/2] cpumask: introduce cpumask for hotpluggable CPUs
Date: Tue, 9 Aug 2011 23:01:57 -0300 [thread overview]
Message-ID: <20110810020157.GA29494@anthem.async.com.br> (raw)
In-Reply-To: <1312940007-26069-2-git-send-email-mturquette@ti.com>
On Tue, Aug 09, 2011 at 06:33:26PM -0700, Mike Turquette wrote:
> - * cpu_possible_mask- has bit 'cpu' set iff cpu is populatable
> - * cpu_present_mask - has bit 'cpu' set iff cpu is populated
> - * cpu_online_mask - has bit 'cpu' set iff cpu available to scheduler
> - * cpu_active_mask - has bit 'cpu' set iff cpu available to migration
> + * cpu_possible_mask - has bit 'cpu' set iff cpu is populatable
> + * cpu_hotpluggable_mask - has bit 'cpu' set iff cpu is hotpluggable
> + * cpu_present_mask - has bit 'cpu' set iff cpu is populated
> + * cpu_online_mask - has bit 'cpu' set iff cpu available to scheduler
> + * cpu_active_mask - has bit 'cpu' set iff cpu available to migration
Why not fix the 'iff' typo while you're here?
--
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs
next prev parent reply other threads:[~2011-08-10 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 1:33 [PATCH 0/2] new " Mike Turquette
2011-08-10 1:33 ` [PATCH 1/2] cpumask: introduce " Mike Turquette
2011-08-10 2:01 ` Christian Robottom Reis [this message]
2011-08-10 2:03 ` Turquette, Mike
2011-08-10 8:42 ` Amit Kucheria
2011-08-10 17:25 ` Turquette, Mike
2011-08-10 1:33 ` [PATCH 2/2] cpu: update cpu_hotpluggable_mask in register_cpu Mike Turquette
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=20110810020157.GA29494@anthem.async.com.br \
--to=kiko@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mturquette@ti.com \
--cc=patches@linaro.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
all inboxes | Powered by JetHome®