From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Miller <davem@davemloft.net>,
linux-arch@vger.kernel.org
Subject: LMB bits
Date: Fri, 09 Jul 2010 17:11:20 +1000 [thread overview]
Message-ID: <1278659480.28659.149.camel@pasglop> (raw)
In-Reply-To: <1278031351-23223-1-git-send-email-yinghai@kernel.org>
So I've pushed the memblocks rename and the modified version of my
patches that Yinghai produced in the "memblock" branch of the
powerpc.git tree, based on top of current Linus tree.
I've left out all the other patches for x86.
I did some compile tests and all my test configs on powerpc pass. I
won't have time to do in depth runtime tests but I will eventually get
to it.
Now we really need the other archs affected by my LMB rework to test
that I haven't broken things for them :-)
I'm especially worried with things like sparc NUMA bits. I think I got
it right but I couldn't test.
So those patches aren't yet candidate for next, though they will be with
a tad more testing.
Cheers,
Ben.
next parent reply other threads:[~2010-07-09 7:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1278031351-23223-1-git-send-email-yinghai@kernel.org>
2010-07-09 7:11 ` Benjamin Herrenschmidt [this message]
2010-07-09 7:24 ` LMB bits Ingo Molnar
2010-07-09 7:28 ` David Miller
2010-07-09 7:33 ` Ingo Molnar
2010-07-09 8:24 ` Geert Uytterhoeven
2010-07-09 13:51 ` Ingo Molnar
2010-07-10 0:20 ` David Miller
2010-07-10 3:55 ` David Miller
2010-07-10 11:01 ` Benjamin Herrenschmidt
2010-07-10 20:14 ` David Miller
2010-07-10 20:53 ` Yinghai Lu
2010-07-12 3:24 ` Benjamin Herrenschmidt
2010-07-12 7:38 ` Benjamin Herrenschmidt
2010-07-12 22:34 ` David Miller
2010-07-13 7:12 ` Benjamin Herrenschmidt
2010-07-13 8:54 ` Ingo Molnar
2010-07-13 15:11 ` Linus Torvalds
2010-07-13 16:45 ` David Miller
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=1278659480.28659.149.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).