linux-kernel - Re: [PATCHSET x86/mm] memblock, x86: Allow node info in memblock and remove x86 specific memblock code

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: <4E1D0F33.7020708@zytor.com>
Date:	Tue, 12 Jul 2011 20:21:23 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Tejun Heo <tj@...nel.org>, mingo@...hat.com, tglx@...utronix.de,
	benh@...nel.crashing.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCHSET x86/mm] memblock, x86: Allow node info in memblock
 and remove x86 specific memblock code

On 07/12/2011 04:26 PM, Yinghai Lu wrote:
> 
> that is great, merge early_node_map into memblock array.
> 
> looks it comes with some mismatch section warning...
> 

I'm also confused about the baseline of the patchset...

	-hpa
--
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/