[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111205210405.GK627@google.com>
Date: Mon, 5 Dec 2011 13:04:05 -0800
From: Tejun Heo <tj@...nel.org>
To: sfr@...b.auug.org.au
Cc: mingo@...e.hu, yinghai@...nel.org, hpa@...or.com,
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, jonas@...thpole.se, lennox.wu@...il.com,
benh@...nel.crashing.org
Subject: linux-next: inclusion request for temporary memblock testing branch
Hello, Stephen.
Can you please include the following branch into linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git memblock-kill-early_node_map
This eventually will go through tip/ but Ingo wants it to be tested a
bit before proceeding.
http://thread.gmane.org/gmane.linux.kernel.cross-arch/11566/focus=1224459
Pulling it into linux-next creates conflicts in three files -
arch/arm/mm/init.c, arch/mips/Kconfig, arch/score/Kconfig. All
conflicts are trivial. Both parties try to add something and
combination of the two work fine. The following branch contains
merged branch for reference.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git memblock-kill-early_node_map-next
allno/modconfig on x86 compile tested. My randomish test kernel seems
to work fine too. I tested building on different archs on good part
of the archs on first posting but my cross build setup is sorta
screwed now and couldn't get much done this time but there hasn't been
any substantial change since the first posting. I'm planning on
getting the cross build env back up soonish once moving is complete.
Thank you.
--
tejun
--
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/
Powered by blists - more mailing lists