linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Please pull 'next' branch of 4xx tree
Date: Tue, 12 Jul 2011 16:41:56 -0400	[thread overview]
Message-ID: <20110712204156.GD4203@zod.rchland.ibm.com> (raw)

Hi Ben,

A few fixes from Tony/Dave, a DTS update from Stefan, and a MAINTAINERS
update.

josh

The following changes since commit af9719c3062dfe216a0c3de3fa52be6d22b4456c:

  powerpc: Use -mtraceback=no (2011-07-01 13:49:27 +1000)

are available in the git repository at:
  ssh://master.kernel.org/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git next

Dave Kleikamp (3):
      powerpc/44x: don't use tlbivax on AMP systems
      powerpc/44x: boot wrapper: allow kernel to load into non-zero address
      powerpc/47x: allow kernel to be loaded in higher physical memory

Josh Boyer (2):
      MAINTAINERS: Update PowerPC 4xx entry
      powerpc/4xx: Move PCIE printk to proper function

Stefan Roese (1):
      powerpc/44x: Use correct phy-address dt nodes on taishan.dts

Tony Breeds (1):
      powerpc/4xx: Add check_link to struct ppc4xx_pciex_hwops

 MAINTAINERS                                   |    2 +-
 arch/powerpc/Kconfig                          |    2 +-
 arch/powerpc/boot/dts/taishan.dts             |    4 +-
 arch/powerpc/boot/treeboot-iss4xx.c           |   23 ++++-
 arch/powerpc/configs/44x/iss476-smp_defconfig |    6 +-
 arch/powerpc/include/asm/mmu.h                |    7 +-
 arch/powerpc/kernel/head_44x.S                |   42 ++++++--
 arch/powerpc/kernel/setup_32.c                |    2 +
 arch/powerpc/mm/44x_mmu.c                     |   13 ++-
 arch/powerpc/mm/tlb_hash32.c                  |    4 +
 arch/powerpc/mm/tlb_nohash.c                  |   19 +++
 arch/powerpc/sysdev/ppc4xx_pci.c              |  147 ++++++++++++++-----------
 12 files changed, 186 insertions(+), 85 deletions(-)

             reply	other threads:[~2011-07-12 20:42 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 20:41 Josh Boyer [this message]
2011-07-20 13:18 ` Please pull 'next' branch of 4xx tree Josh Boyer
2011-07-21  9:22   ` Benjamin Herrenschmidt
  -- 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-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-09-28 13:09 Josh Boyer
2010-10-13 13:16 ` Josh Boyer
2010-10-14  0:56   ` Benjamin Herrenschmidt
2010-10-14 10:35     ` 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=20110712204156.GD4203@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --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).