LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: torvalds@linux-foundation.org
Cc: linuxppc-dev@ozlabs.org, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Please pull powerpc.git for-2.6.25 branch
Date: Fri, 8 Feb 2008 20:56:59 +1100	[thread overview]
Message-ID: <18348.10091.120122.608010@cargo.ozlabs.ibm.com> (raw)

Linus,

Please do

git pull \
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git for-2.6.25

to get some bug-fixes for powerpc (1 for powermac and 8 for Cell),
plus 3 commits from Badari Pulavarty that implement memory hot-remove
for 64-bit powerpc.  These 3 commits have been signed-off by Andrew
Morton.  One of them touches generic code (kernel/resource.c), and it
has been acked by KAMEZAWA Hiroyuki.

Thanks,
Paul.

 arch/powerpc/Kconfig                            |    6 +++
 arch/powerpc/mm/mem.c                           |   33 +++++++++++++++
 arch/powerpc/platforms/cell/iommu.c             |   48 +++++++++++++----------
 arch/powerpc/platforms/cell/spufs/backing_ops.c |    6 +++
 arch/powerpc/platforms/cell/spufs/fault.c       |   12 ++----
 arch/powerpc/platforms/cell/spufs/file.c        |   49 ++++++++++++++---------
 arch/powerpc/platforms/cell/spufs/run.c         |   21 ++++++----
 arch/powerpc/platforms/cell/spufs/spufs.h       |    5 ++
 arch/powerpc/platforms/powermac/feature.c       |   11 +++++
 drivers/macintosh/smu.c                         |   25 +++++++++++-
 include/asm-powerpc/pmac_feature.h              |    8 ++++
 kernel/resource.c                               |    2 -
 12 files changed, 166 insertions(+), 60 deletions(-)

Badari Pulavarty (3):
      [POWERPC] Add remove_memory() for 64-bit powerpc
      [POWERPC] Enable hotplug memory remove for 64-bit powerpc
      [POWERPC] Add arch-specific walk_memory_remove() for 64-bit powerpc

Benjamin Herrenschmidt (1):
      [POWERPC] Disable G5 NAP mode during SMU commands on U3

Christoph Hellwig (1):
      [POWERPC] spufs: Fix state_mutex leaks

Luke Browning (2):
      [POWERPC] spufs: No need to have a runnable SPU for libassist update
      [POWERPC] spufs: Fix timing dependent false return from spufs_run_spu

Masato Noguchi (1):
      [POWERPC] spufs: Update SPU_Status[CISHP] in backing runcntl write

Michael Ellerman (4):
      [POWERPC] Fix cell IOMMU null pointer explosion on old firmwares
      [POWERPC] Don't enable cell IOMMU fixed mapping if there are no dma-ranges
      [POWERPC] Fix potential cell IOMMU bug when switching back to default DMA ops
      [POWERPC] Make cell IOMMU fixed mapping printk more useful

             reply	other threads:[~2008-02-08  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08  9:56 Paul Mackerras [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-07  3:22 Please pull powerpc.git for-2.6.25 branch Paul Mackerras
2008-02-07  5:26 ` Grant Likely
2008-02-07  5:27   ` Tony Breeds
2008-02-07 11:19 ` Paul Mackerras
2008-01-31  1:23 Paul Mackerras

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=18348.10091.120122.608010@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=torvalds@linux-foundation.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