From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: powerpc.git merge status
Date: Tue, 15 Jul 2008 07:55:12 -0400 [thread overview]
Message-ID: <1216122912.14579.52.camel@weaponx> (raw)
In-Reply-To: <1216101729.7740.84.camel@pasglop>
On Tue, 2008-07-15 at 16:02 +1000, Benjamin Herrenschmidt wrote:
> Now, regarding the remaining bits, still on my todo for the next batch,
> probably later this week, in this merge window:
<snip>
> - Kumar PTE bits... that's a bit "hot" for this merge window
> but I suppose it can still make it.
I'd argue that they should make it. It's parity with your PTE rework
for 44x, and Kumar even found a bug (which you've pulled the fix for) in
your implementation :).
josh
next prev parent reply other threads:[~2008-07-15 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 6:02 powerpc.git merge status Benjamin Herrenschmidt
2008-07-15 6:16 ` Grant Likely
2008-07-15 8:01 ` Benjamin Herrenschmidt
2008-07-15 11:39 ` Anton Vorontsov
2008-07-17 6:30 ` Benjamin Herrenschmidt
2008-07-15 11:55 ` Josh Boyer [this message]
2008-07-15 12:52 ` Kumar Gala
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=1216122912.14579.52.camel@weaponx \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).