From: Andy Whitcroft <apw@shadowen.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Chad Reese <creese@caviumnetworks.com>
Subject: Re: mem_map definition / declaration.
Date: Wed, 31 May 2006 18:00:29 +0100 [thread overview]
Message-ID: <447DCBAD.8070307@shadowen.org> (raw)
In-Reply-To: <20060531162345.GA19674@linux-mips.org>
Ralf Baechle wrote:
> mm/memory defines mem_map and max_mapnr only if !CONFIG_NEED_MULTIPLE_NODES.
> <linux/mm.h> declares mem_map[] if !CONFIG_DISCONTIGMEM. Shouldn't
> both depend on !CONFIG_FLATMEM? As things are now mem_map may be
> declared but not defined for a non-NUMA sparsemem system which may make
> tracking a remaining mem_map reference in the code a little harder.
Sounds suspect for sure. I will take a look and see. Thanks for the
head up.
-apw
next prev parent reply other threads:[~2006-05-31 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 16:23 mem_map definition / declaration Ralf Baechle
2006-05-31 17:00 ` Andy Whitcroft [this message]
2006-06-09 13:48 ` [PATCH] mem_map is part of the FLATMEM model Andy Whitcroft
2006-06-10 0:23 ` Andrew Morton
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=447DCBAD.8070307@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=creese@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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