From: Ingo Molnar <mingo@elte.hu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Yinghai Lu <yinghai@kernel.org>, "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: Re: LMB bits
Date: Fri, 9 Jul 2010 09:24:08 +0200 [thread overview]
Message-ID: <20100709072408.GD10743@elte.hu> (raw)
In-Reply-To: <1278659480.28659.149.camel@pasglop>
* Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 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 guess that means this URI:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git memblock
right?
> 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.
Thanks Ben.
Dave, can you confirm that it works fine on Sparc? If it does then i'd like to
pull your tree and use it as a base from that point on. I can push it to
linux-next as well and treat it together with Yinghai's x86 changes. Would
that be fine with you, or would you like to push it to Linus?
Also, after some testing we could send the tree cut at this point:
506e7de: lmb: rename to memblock
to Linus straight away - to get the big rename out of the way:
74 files changed, 1039 insertions(+), 1039 deletions(-)
Hm?
Ingo
next prev parent reply other threads:[~2010-07-09 7:24 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 ` LMB bits Benjamin Herrenschmidt
2010-07-09 7:24 ` Ingo Molnar [this message]
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=20100709072408.GD10743@elte.hu \
--to=mingo@elte.hu \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--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).