linux-kernel - Re: [PATCH] memblock: Kill ARCH_POPULATES_NODE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51499748.8020700@monstr.eu>
Date:	Wed, 20 Mar 2013 12:02:32 +0100
From:	Michal Simek <monstr@...str.eu>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	Tejun Heo <tj@...nel.org>, James Hogan <james.hogan@...tec.com>,
	microblaze-uclinux@...e.uq.edu.au, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] memblock: Kill ARCH_POPULATES_NODE_MAP once more

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@...str.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 this patch,
Michal

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/