From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: "next" branch update
Date: Tue, 28 Jul 2009 14:14:53 +1000 [thread overview]
Message-ID: <1248754493.30993.47.camel@pasglop> (raw)
So I opened powerpc-next, and pushed the pile that was in "test" (with
an additional bug fix to one of my patches that was causing the crash
at boot that mpe reported with hugetlbfs enabled).
The pre-req patch for adding an argument to __pte_free_tlb() has already
been merged upstream by Linus.
Now is time for people who want things into 2.6.32 to be noisy about it.
Cheers,
Ben.
next reply other threads:[~2009-07-28 4:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 4:14 Benjamin Herrenschmidt [this message]
2009-07-28 7:54 ` "next" branch update Martyn Welch
-- strict thread matches above, loose matches on Subject: below --
2009-06-12 7:29 Benjamin Herrenschmidt
2009-06-12 13:54 ` Timur Tabi
2009-06-12 13:59 ` Benjamin Herrenschmidt
2009-06-10 3:14 Benjamin Herrenschmidt
2009-06-10 4:13 ` Grant Likely
2009-06-10 6:07 ` Timur Tabi
2009-06-11 17:05 ` Josh Boyer
2009-06-02 3:03 Benjamin Herrenschmidt
2009-06-02 3:26 ` Grant Likely
2009-06-02 3:44 ` 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=1248754493.30993.47.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).