From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Kumar Gala <galak@gate.crashing.org>
Subject: powerpc-next rebased (again)
Date: Thu, 20 Aug 2009 14:40:39 +1000 [thread overview]
Message-ID: <1250743239.10937.1.camel@pasglop> (raw)
In-Reply-To: <4177854C-965A-4A26-A517-B6F0B48703BD@kernel.crashing.org>
Ok so due to screwup mentioned earlier, it's rebased agian :-(
Hopefully that's the last time for very looooooong...
While at it, I removed the lmb kmemleak patch from Michael since
we decided it wasn't a good idea and added Kumar's fix for
assert_pte_locked().
I also updated the test branch with more stuff such as Fujita
IOMMU bits and pieces.
Cheers,
Ben.
next prev parent reply other threads:[~2009-08-20 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 7:33 powerpc-next rebased Benjamin Herrenschmidt
2009-08-19 13:43 ` Kumar Gala
2009-08-19 13:54 ` Kumar Gala
2009-08-19 14:35 ` Kumar Gala
2009-08-20 4:40 ` Benjamin Herrenschmidt [this message]
2009-08-19 21:56 ` Benjamin Herrenschmidt
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=1250743239.10937.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@gate.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).