From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Anton Vorontsov <anton.vorontsov@linaro.org>
Subject: Re: [PATCH] cpu remove CONFIG_INIT_ALL_POSSIBLE check
Date: Wed, 15 May 2013 13:58:52 +0530 [thread overview]
Message-ID: <51934744.9010803@linux.vnet.ibm.com> (raw)
In-Reply-To: <1368604214-23237-1-git-send-email-lig.fnst@cn.fujitsu.com>
On 05/15/2013 01:20 PM, liguang wrote:
> seems CONFIG_INIT_ALL_POSSIBLE is obsolete now.
>
Um? A simple grep showed me this:
arch/s390/Kconfig: select INIT_ALL_POSSIBLE
arch/m32r/Kconfig: select INIT_ALL_POSSIBLE
arch/parisc/Kconfig: select INIT_ALL_POSSIBLE
init/Kconfig:config INIT_ALL_POSSIBLE
Regards,
Srivatsa S. Bhat
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
> kernel/cpu.c | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index cd166d3..2697d1a 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -662,12 +662,7 @@ EXPORT_SYMBOL_GPL(cpu_bit_bitmap);
> const DECLARE_BITMAP(cpu_all_bits, NR_CPUS) = CPU_BITS_ALL;
> EXPORT_SYMBOL(cpu_all_bits);
>
> -#ifdef CONFIG_INIT_ALL_POSSIBLE
> -static DECLARE_BITMAP(cpu_possible_bits, CONFIG_NR_CPUS) __read_mostly
> - = CPU_BITS_ALL;
> -#else
> static DECLARE_BITMAP(cpu_possible_bits, CONFIG_NR_CPUS) __read_mostly;
> -#endif
> const struct cpumask *const cpu_possible_mask = to_cpumask(cpu_possible_bits);
> EXPORT_SYMBOL(cpu_possible_mask);
>
next prev parent reply other threads:[~2013-05-15 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 7:50 liguang
2013-05-15 8:28 ` Srivatsa S. Bhat [this message]
2013-05-15 8:46 ` li guang
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=51934744.9010803@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=anton.vorontsov@linaro.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®