From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: powerpc-next rebased
Date: Wed, 19 Aug 2009 17:33:52 +1000 [thread overview]
Message-ID: <1250667232.4810.20.camel@pasglop> (raw)
Allright it's done, let's hope I didn't screw up :-)
So I rebased the whole thing on top of latest upstream, fixing along the
way the bug that Becky found in tlb.h and fixing up a commit name from
Kumar that was referencing the wrong board. I also applied to -next the
remaining things that were in -test, except for my _PAGE_EXEC rework.
I've added a Kumar's fix for assert_pte_locked() and merged Paulus per
counter callchain support while at it
I also pushed out an updated -test with the new variant of the
_PAGE_EXEC rework and a couple more things hanging off patchwork, I'll
probably add a bit more such as the pending iommu bits tomorrow.
Cheers,
Ben.
next reply other threads:[~2009-08-19 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 7:33 Benjamin Herrenschmidt [this message]
2009-08-19 13:43 ` powerpc-next rebased Kumar Gala
2009-08-19 13:54 ` Kumar Gala
2009-08-19 14:35 ` Kumar Gala
2009-08-20 4:40 ` powerpc-next rebased (again) Benjamin Herrenschmidt
2009-08-19 21:56 ` powerpc-next rebased 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=1250667232.4810.20.camel@pasglop \
--to=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).