From: Kumar Gala <galak@kernel.crashing.org>
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:52:44 -0500 [thread overview]
Message-ID: <6EB5960B-C8EC-4404-9F64-E241ED1A909F@kernel.crashing.org> (raw)
In-Reply-To: <1216101729.7740.84.camel@pasglop>
On Jul 15, 2008, at 1:02 AM, Benjamin Herrenschmidt wrote:
> I've pulled from Kumar, Josh and Grant, along with applying some
> patches hand picked from patchworks and build fixes. I've merged in
> Linus as of today (minus David Woodhouse firmware patches that have a
> build breakage) in order to fix a (fairly trivial) merge conflict.
>
> I've now pushed that to my powerpc.git "master" branch for overnight
> build-testing with kisskb at which point
>
> If all goes well, I'll put all of that in "merge" and "next" and ask
> Linus to pull it tomorrow.
>
> Now, regarding the remaining bits, still on my todo for the next
> batch,
> probably later this week, in this merge window:
>
> - The CMO stuff, I need to have a closer look but it should
> probably go in
> - Milton's serie. Mostly fixes, haven't had time to look too
> closely yet.
> - Kumar PTE bits... that's a bit "hot" for this merge window
> but I suppose it can still make it.
> - Some Cell stuff for which I'm waiting a new serie from Arnd
>
> If you believe I've missed something, now is time to be vocal about
> it :-)
There are a number of patches I still need to pick up but I expect
this to be a second round of pulling.
- k
prev parent reply other threads:[~2008-07-15 12:52 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
2008-07-15 12:52 ` Kumar Gala [this message]
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=6EB5960B-C8EC-4404-9F64-E241ED1A909F@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--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).