linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Please pull from 'next' branch (2.6.29)
Date: Tue, 13 Jan 2009 09:21:57 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0901130917190.21289@blarg.am.freescale.net> (raw)

Please pull from 'next' branch of

(this is my last pull request of 'next' for 2.6.29.  I would like to see
the 'powerpc: Unify opcode definitions and support' patch go in but leave
that for you to pull in directly).

	master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git next

to receive the following updates:

 arch/powerpc/Kconfig                           |   18 +
 arch/powerpc/boot/dts/mpc8315erdb.dts          |   68 ++++++
 arch/powerpc/boot/dts/mpc8377_mds.dts          |   64 ++++++
 arch/powerpc/boot/dts/mpc8377_rdb.dts          |   64 ++++++
 arch/powerpc/boot/dts/mpc8378_mds.dts          |   64 ++++++
 arch/powerpc/boot/dts/mpc8378_rdb.dts          |   64 ++++++
 arch/powerpc/include/asm/reg_booke.h           |    1
 arch/powerpc/kernel/Makefile                   |    1
 arch/powerpc/kernel/cpu_setup_fsl_booke.S      |   31 +++
 arch/powerpc/kernel/cputable.c                 |    8
 arch/powerpc/kernel/head_booke.h               |    6
 arch/powerpc/kernel/head_fsl_booke.S           |   85 +++++---
 arch/powerpc/mm/fsl_booke_mmu.c                |   93 ++++-----
 arch/powerpc/platforms/83xx/Makefile           |    1
 arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c |  209 +++++++++++++++++++++
 arch/powerpc/platforms/83xx/mpc831x_rdb.c      |    2
 arch/powerpc/platforms/83xx/mpc837x_mds.c      |   10 -
 arch/powerpc/platforms/83xx/mpc837x_rdb.c      |    2
 arch/powerpc/platforms/Kconfig                 |   11 +
 arch/powerpc/sysdev/fsl_pci.c                  |  244 ++++++++++++++++++++++---
 drivers/i2c/chips/Kconfig                      |   11 -
 drivers/i2c/chips/Makefile                     |    1
 drivers/i2c/chips/mcu_mpc8349emitx.c           |  209 ---------------------
 include/linux/pci_ids.h                        |    8
 24 files changed, 941 insertions(+), 334 deletions(-)

Anton Vorontsov (4):
      powerpc/fsl_pci: Add MPC83xx PCI-E controller RC mode support
      powerpc/83xx: Add PCI-E support for all MPC83xx boards with PCI-E
      powerpc/83xx: Make serial ports work on MPC8315E-RDB w/ FSL U-Boots
      powerpc/83xx: Move mcu_mpc8349emitx driver out of drivers/i2c/chips/

Kumar Gala (2):
      powerpc/fsl-booke: Cleanup init/exception setup to be runtime
      powerpc/e500mc: Doorbells need to be taken w/exceptions disabled

Trent Piepho (3):
      powerpc/fsl-booke: Remove code duplication in lowmem mapping
      powerpc/fsl-booke: Allow larger CAM sizes than 256 MB
      powerpc/fsl-booke: Make CAM entries used for lowmem configurable

             reply	other threads:[~2009-01-13 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 15:21 Kumar Gala [this message]
2009-01-13 20:59 ` Please pull from 'next' branch (2.6.29) Benjamin Herrenschmidt
2009-01-13 21:17   ` Kumar Gala
2009-01-13 21:22     ` Kumar Gala
2009-01-13 23:36     ` 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=Pine.LNX.4.64.0901130917190.21289@blarg.am.freescale.net \
    --to=galak@kernel.crashing.org \
    --cc=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).