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
Date: Thu, 6 Aug 2009 22:09:48 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0908062209340.7477@localhost.localdomain> (raw)

Please pull from 'next' branch of

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

to receive the following updates:

 arch/powerpc/boot/dts/gef_sbc310.dts      |   64 +++-
 arch/powerpc/boot/dts/mgcoge.dts          |   53 +++
 arch/powerpc/boot/dts/mpc8377_rdb.dts     |    2
 arch/powerpc/boot/dts/mpc8377_wlan.dts    |  464 +++++++++++++++++++++++++++++
 arch/powerpc/boot/dts/mpc8378_rdb.dts     |    2
 arch/powerpc/boot/dts/mpc8379_rdb.dts     |    2
 arch/powerpc/boot/dts/mpc8536ds.dts       |   32 +-
 arch/powerpc/boot/dts/mpc8536ds_36b.dts   |  467 ++++++++++++++++++++++++++++++
 arch/powerpc/boot/dts/mpc8548cds.dts      |   20 +
 arch/powerpc/mm/fsl_booke_mmu.c           |    2
 arch/powerpc/platforms/82xx/mgcoge.c      |   69 +++-
 arch/powerpc/platforms/83xx/Kconfig       |    4
 arch/powerpc/platforms/83xx/mpc837x_rdb.c |   28 +
 arch/powerpc/platforms/83xx/mpc83xx.h     |    4
 arch/powerpc/platforms/86xx/gef_ppc9a.c   |   37 +-
 arch/powerpc/sysdev/fsl_rio.c             |   18 -
 arch/powerpc/sysdev/ipic.c                |    7
 arch/powerpc/sysdev/qe_lib/qe_ic.c        |    5
 18 files changed, 1219 insertions(+), 61 deletions(-)

Anton Vorontsov (3):
      powerpc/83xx: Add support for MPC8377E-WLAN boards
      powerpc/85xx: Add support for I2C EEPROMs on MPC8548CDS boards
      powerpc/83xx: Add eSDHC support for MPC837xE-RDB/WLAN boards

Heiko Schocher (1):
      powerpc/82xx: mgcoge - updates for 2.6.32

Julia Lawall (3):
      powerpc/fsl_rio: Add kmalloc NULL tests
      powerpc/ipic: introduce missing kfree
      powerpc/qe: introduce missing kfree

Kumar Gala (2):
      powerpc/85xx: Move mpc8536ds.dts to address-cells/size-cells = <2>
      powerpc/85xx: Added 36-bit physical device tree for mpc8572ds board

Martyn Welch (3):
      powerpc/86xx: Correct reading of information presented in cpuinfo
      powerpc/86xx: Enable XMC site on GE Fanuc SBC310
      powerpc/86xx: Update GE Fanuc sbc310 DTS

Roel Kluin (1):
      powerpc/fsl-booke: read buffer overflow

Sebastian Andrzej Siewior (1):
      powerpc/ipic: unmask all interrupt sources

             reply	other threads:[~2009-08-07  3:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07  3:09 Kumar Gala [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-19  5:53 Please pull from 'next' branch Kumar Gala
2009-05-13 22:33 Kumar Gala
2009-03-27 22:43 Kumar Gala
2009-03-19  9:05 Kumar Gala
2009-03-10 19:00 Kumar Gala
2009-02-23 16:26 Kumar Gala
2009-02-17 21:52 Kumar Gala
2009-02-18  2:22 ` Benjamin Herrenschmidt
2009-02-18  3:04   ` Kumar Gala
2009-02-18  3:13     ` Benjamin Herrenschmidt
2009-01-07 21:34 Kumar Gala
2008-12-30 17:40 Kumar Gala
2008-12-30 18:31 ` Kumar Gala
2008-12-15 20:31 Kumar Gala
2008-12-16 16:51 ` Anton Vorontsov
2008-12-03 15:54 Kumar Gala

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.0908062209340.7477@localhost.localdomain \
    --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).