From: Ralf Baechle <ralf@linux-mips.org>
To: Tejun Heo <tj@kernel.org>
Cc: benh@kernel.crashing.org, yinghai@kernel.org, hpa@zytor.com,
tony.luck@intel.com, schwidefsky@de.ibm.com,
liqin.chen@sunplusct.com, lethal@linux-sh.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, mingo@redhat.com,
linux-mips@linux-mips.org
Subject: Re: [PATCH 19/23] mips: Use HAVE_MEMBLOCK_NODE_MAP
Date: Wed, 3 Aug 2011 17:17:45 +0100 [thread overview]
Message-ID: <20110803161745.GA13266@linux-mips.org> (raw)
In-Reply-To: <1311694534-5161-20-git-send-email-tj@kernel.org>
On Tue, Jul 26, 2011 at 05:35:30PM +0200, Tejun Heo wrote:
> mips used early_node_map[] just to prime free_area_init_nodes(). Now
> memblock can be used for the same purpose and early_node_map[] is
> scheduled to be dropped. Use memblock instead.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: linux-mips@linux-mips.org
> ---
> Only compile tested. Thanks.
>
> arch/mips/Kconfig | 3 +++
> arch/mips/kernel/setup.c | 3 ++-
> arch/mips/sgi-ip27/ip27-memory.c | 5 +++--
> 3 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 653da62..368b2ec 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -24,6 +24,9 @@ config MIPS
> select GENERIC_IRQ_PROBE
> select GENERIC_IRQ_SHOW
> select HAVE_ARCH_JUMP_LABEL
> + select HAVE_MEMBLOCK
This means <linux/memblock.h> will include <asm/memblock.h> which does
not exist for MIPS. Did you accidentally not post this new file?
Ralf
next prev parent reply other threads:[~2011-08-03 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1311694534-5161-1-git-send-email-tj@kernel.org>
2011-07-26 15:35 ` [PATCH 19/23] mips: Use HAVE_MEMBLOCK_NODE_MAP Tejun Heo
2011-08-03 16:17 ` Ralf Baechle [this message]
2011-08-03 16:26 ` Tejun Heo
[not found] <1322508685-32532-1-git-send-email-tj@kernel.org>
2011-11-28 19:31 ` Tejun Heo
2011-12-08 16:19 ` Ralf Baechle
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=20110803161745.GA13266@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=liqin.chen@sunplusct.com \
--cc=mingo@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=yinghai@kernel.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