From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull from 'next' branch
Date: Wed, 18 Feb 2009 13:22:52 +1100 [thread overview]
Message-ID: <1234923772.14060.322.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0902171551460.23647@blarg.am.freescale.net>
> I'd also like the opcode patch to go in since several patches depend on
> that (doorbell, tlbilx). If you want to ack the patch I can put it into
> my next branch for you.
It's already in my test branch, which for some reason I forgot to push
out... Doing some updates now, you'll get it.
Cheers,
Ben.
next prev parent reply other threads:[~2009-02-18 2:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 21:52 Please pull from 'next' branch Kumar Gala
2009-02-18 2:22 ` Benjamin Herrenschmidt [this message]
2009-02-18 3:04 ` Kumar Gala
2009-02-18 3:13 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2009-08-07 3:09 Kumar Gala
2009-05-19 5:53 Kumar Gala
2009-05-13 22:33 Kumar Gala
2009-03-27 22:43 Kumar Gala
2009-03-19 9:05 Kumar Gala
2009-03-10 19:00 Kumar Gala
2009-02-23 16:26 Kumar Gala
2009-01-07 21:34 Kumar Gala
2008-12-30 17:40 Kumar Gala
2008-12-30 18:31 ` Kumar Gala
2008-12-15 20:31 Kumar Gala
2008-12-16 16:51 ` Anton Vorontsov
2008-12-03 15:54 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=1234923772.14060.322.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@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).