From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Please pull 'next' branch of 4xx tree
Date: Thu, 14 Oct 2010 11:56:15 +1100 [thread overview]
Message-ID: <1287017775.2205.49.camel@pasglop> (raw)
In-Reply-To: <20101013131608.GA6154@zod.rchland.ibm.com>
On Wed, 2010-10-13 at 09:16 -0400, Josh Boyer wrote:
> On Tue, Sep 28, 2010 at 09:09:41AM -0400, Josh Boyer wrote:
> >Hi Ben,
> >
> >A few small updates for the next branch. A new board/SoC from AMCC, and
> >some 476 changes from Shaggy. Please pull.
>
> OK, below is a fixed up tree that drops the patch Shaggy said was
> broken, and rebases on top of your new -next branch. Please pull.
please, rebase again without Shaggy's lazy flush patch. I'll handle that
one separately, I think it needs a little bit more massaging.
Cheers,
Ben.
> josh
>
> The following changes since commit 4108d9ba9091c55cfb968d42dd7dcae9a098b876:
>
> powerpc/Makefiles: Change to new flag variables (2010-10-13 16:19:22 +1100)
>
> are available in the git repository at:
> ssh://master.kernel.org/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git next
>
> Dave Kleikamp (1):
> powerpc/476: lazy flush_tlb_mm for nohash architectures
>
> Josh Boyer (1):
> powerpc/44x: Update ppc44x_defconfig
>
> Tirumala Marri (1):
> powerpc/44x: Add support for the AMCC APM821xx SoC
>
> arch/powerpc/boot/dts/bluestone.dts | 254 ++++++++++++++++++++++++++
> arch/powerpc/configs/44x/bluestone_defconfig | 68 +++++++
> arch/powerpc/configs/ppc44x_defconfig | 9 +-
> arch/powerpc/kernel/cpu_setup_44x.S | 1 +
> arch/powerpc/kernel/cputable.c | 15 ++
> arch/powerpc/mm/mmu_context_nohash.c | 154 ++++++++++++++--
> arch/powerpc/mm/mmu_decl.h | 8 +
> arch/powerpc/mm/tlb_nohash.c | 28 +++-
> arch/powerpc/platforms/44x/Kconfig | 16 ++
> arch/powerpc/platforms/44x/ppc44x_simple.c | 1 +
> 10 files changed, 534 insertions(+), 20 deletions(-)
> create mode 100644 arch/powerpc/boot/dts/bluestone.dts
> create mode 100644 arch/powerpc/configs/44x/bluestone_defconfig
next prev parent reply other threads:[~2010-10-14 0:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 13:09 Please pull 'next' branch of 4xx tree Josh Boyer
2010-10-13 13:16 ` Josh Boyer
2010-10-14 0:56 ` Benjamin Herrenschmidt [this message]
2010-10-14 10:35 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2012-05-02 13:51 Josh Boyer
2012-05-09 11:42 ` Josh Boyer
2012-03-16 13:41 Josh Boyer
2012-03-16 14:50 ` Stephen Rothwell
2011-12-20 16:23 Josh Boyer
2011-12-21 20:11 ` Josh Boyer
2011-08-10 18:26 Josh Boyer
2011-08-29 13:05 ` Josh Boyer
2011-08-30 3:09 ` Benjamin Herrenschmidt
2011-07-12 20:41 Josh Boyer
2011-07-20 13:18 ` Josh Boyer
2011-07-21 9:22 ` Benjamin Herrenschmidt
2011-06-28 12:07 Josh Boyer
2011-02-15 14:54 Josh Boyer
2011-03-15 13:19 ` Josh Boyer
2010-12-03 13:22 Josh Boyer
2010-07-26 16:58 Josh Boyer
2010-05-05 17:11 Josh Boyer
2010-02-12 13:02 Josh Boyer
2009-12-18 14:08 Josh Boyer
2009-12-04 14:38 Josh Boyer
2009-11-04 18:55 Josh Boyer
2009-11-19 14:45 ` Josh Boyer
2009-11-19 14:49 ` Kumar Gala
2009-11-20 8:53 ` Benjamin Herrenschmidt
2009-08-31 16:24 Josh Boyer
2009-07-31 12:50 Josh Boyer
2008-12-11 15:09 Josh Boyer
2008-10-20 13:14 Josh Boyer
2008-10-21 0:04 ` Josh Boyer
2008-10-03 12:30 Josh Boyer
2008-09-18 13:26 Josh Boyer
2008-07-09 18:13 Josh Boyer
2008-06-19 17:53 Josh Boyer
2008-05-29 15:40 Josh Boyer
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=1287017775.2205.49.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.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).