From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-arch@vger.kernel.org, Dave Hansen <haveblue@us.ibm.com>
Subject: Re: no-arch-specific-mem_map-init
Date: Thu, 10 Mar 2005 15:35:34 +0200 [thread overview]
Message-ID: <20050310133534.GD32607@linux-sh.org> (raw)
In-Reply-To: <20050309225833.6d80fc42.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Wed, Mar 09, 2005 at 10:58:33PM -0800, Andrew Morton wrote:
> From: Dave Hansen <haveblue@us.ibm.com>
>
> So, I had to make sure to initialize the global mem_map[] before calling
> into free_area_init_node(). Then, I realized how many architectures do
> this on their own, and have comments like this:
>
> /* XXX: MRB-remove - this doesn't seem sane, should this be done somewhere else ?*/
> mem_map = NODE_DATA(0)->node_mem_map;
>
I don't see any problems with this patch either. At least it works fine
for sh64 as well (and sh, where this comment originated).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-10 13:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 6:58 no-arch-specific-mem_map-init Andrew Morton
2005-03-10 7:38 ` no-arch-specific-mem_map-init Martin J. Bligh
2005-03-10 8:22 ` no-arch-specific-mem_map-init Paul Mackerras
2005-03-10 13:35 ` Paul Mundt [this message]
2005-03-10 14:18 ` no-arch-specific-mem_map-init Matthew Wilcox
2005-03-10 14:30 ` no-arch-specific-mem_map-init David Howells
2005-03-10 14:33 ` no-arch-specific-mem_map-init Matthew Wilcox
2005-03-10 15:24 ` no-arch-specific-mem_map-init Randolph Chung
2005-03-10 15:26 ` no-arch-specific-mem_map-init Martin J. Bligh
2005-03-10 15:58 ` no-arch-specific-mem_map-init Dave Hansen
2005-03-10 16:21 ` no-arch-specific-mem_map-init Matthew Wilcox
2005-03-10 22:54 ` no-arch-specific-mem_map-init Russell King
-- strict thread matches above, loose matches on Subject: below --
2005-03-10 19:59 no-arch-specific-mem_map-init Luck, Tony
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=20050310133534.GD32607@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-arch@vger.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