linux-kernel - Re: [PATCHSET tip:x86/memblock] memblock: Kill early_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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 26 Jul 2011 15:20:04 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Tejun Heo <tj@...nel.org>
CC:	Yinghai Lu <yhlu.kernel@...il.com>, Ingo Molnar <mingo@...e.hu>,
	benh@...nel.crashing.org, tony.luck@...el.com, ralf@...ux-mips.org,
	schwidefsky@...ibm.com, liqin.chen@...plusct.com,
	lethal@...ux-sh.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	mingo@...hat.com
Subject: Re: [PATCHSET tip:x86/memblock] memblock: Kill early_node_map[]

On 07/26/2011 02:49 PM, Tejun Heo wrote:
> Hello,
> 
> On Tue, Jul 26, 2011 at 11:14 PM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
>> it passes test with my x86 64bits setups.
> 
> Great, thanks for testing.
> 
>> looks like tip/master does not include tip/x86/memblock and tip/x86/mm yet.
>>
>> So tip/x86/memblock, tip/x86/mm will not get into 3.1?
> 
> Yeah, I think the whole thing including the last patchset was a bit
> too late for this merge window.  These are basically cleanups and
> could possibly cause weird boot regressions, so having enough time in
> -tip before going mainline seems like a good idea to me.
> 

It seems a bit scary, so holding this until 3.2 would definitely be my
preference.

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