From: Tejun Heo <tj@kernel.org>
To: sfr@canb.auug.org.au
Cc: mingo@elte.hu, yinghai@kernel.org, hpa@zytor.com,
tony.luck@intel.com, ralf@linux-mips.org, schwidefsky@de.ibm.com,
liqin.chen@sunplusct.com, lethal@linux-sh.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, mingo@redhat.com, jonas@southpole.se,
lennox.wu@gmail.com, benh@kernel.crashing.org
Subject: linux-next: inclusion request for temporary memblock testing branch
Date: Mon, 5 Dec 2011 13:04:05 -0800 [thread overview]
Message-ID: <20111205210405.GK627@google.com> (raw)
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
next reply other threads:[~2011-12-05 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 21:04 Tejun Heo [this message]
2011-12-05 21:59 ` linux-next: inclusion request for temporary memblock testing branch Stephen Rothwell
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=20111205210405.GK627@google.com \
--to=tj@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jonas@southpole.se \
--cc=lennox.wu@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--cc=yinghai@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