From: James Hogan <james.hogan@imgtec.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: <monstr@monstr.eu>, Tejun Heo <tj@kernel.org>,
<microblaze-uclinux@itee.uq.edu.au>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memblock: Kill ARCH_POPULATES_NODE_MAP once more
Date: Wed, 20 Mar 2013 13:07:18 +0000 [thread overview]
Message-ID: <5149B486.9050406@imgtec.com> (raw)
In-Reply-To: <51499748.8020700@monstr.eu>
On 20/03/13 11:02, Michal Simek wrote:
> On 03/20/2013 11:25 AM, Paul Bolle wrote:
>> The Kconfig symbol ARCH_POPULATES_NODE_MAP was killed in v3.3. After
>> that it popped up again in microblaze and metag. Nobody noticed,
>> probably because these Kconfig symbols are entirely unused and these
>> architectures both select HAVE_MEMBLOCK_NODE_MAP. Anyhow, these two
>> entries can also be killed.
>
> Ah. We have done the developing on that on earlier version and
> to mainline it went in 3.3 merge window that's why I didn't notice it.
>
> If James wants to take this patch through his tree, I am ok with that
> and here is my
>
> Acked-by: Michal Simek <monstr@monstr.eu>
>
> Or if you want to take this through my microblaze tree, I am also ok
> with that but please send me your ACK.
Thanks for the patch Paul. This was added to metag when we were on
2.6.34. I spotted the adding of HAVE_MEMBLOCK_NODE_MAP to SH in v3.3 and
did the same for metag, but didn't notice the removal of
ARCH_POPULATES_NODE_MAP.
I'm happy to take this patch for v3.10.
Cheers
James
next prev parent reply other threads:[~2013-03-20 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 10:25 [PATCH] memblock: Kill ARCH_POPULATES_NODE_MAP once more Paul Bolle
2013-03-20 11:02 ` Michal Simek
2013-03-20 13:07 ` James Hogan [this message]
2013-03-20 14:00 ` Michal Simek
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=5149B486.9050406@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
--cc=pebolle@tiscali.nl \
--cc=tj@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