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, Paul Mackerras <paulus@samba.org>
Subject: Please pull from 'pci' branch into 'test'
Date: Tue, 5 May 2009 07:26:34 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0905050721500.18785@localhost.localdomain> (raw)

Ben,

Here are various pci related changes for 2.6.31 that can look at going
into your test tree to see if they break anyone.  It would be nice if this
could get some testing on pseries by one of you guys as I have no access
to such HW.

- k

Please pull from 'pci' branch of

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

to receive the following updates:

 arch/powerpc/include/asm/pci-bridge.h          |    7 ------
 arch/powerpc/kernel/pci_32.c                   |   19 ----------------
 arch/powerpc/kernel/pci_64.c                   |   10 --------
 arch/powerpc/kernel/pci_dn.c                   |   28 -------------------------
 arch/powerpc/kernel/rtas_pci.c                 |   10 +-------
 arch/powerpc/platforms/52xx/efika.c            |    4 +--
 arch/powerpc/platforms/52xx/mpc52xx_pci.c      |    4 +--
 arch/powerpc/platforms/cell/celleb_pci.c       |   10 +-------
 arch/powerpc/platforms/cell/celleb_scc_epci.c  |   13 +----------
 arch/powerpc/platforms/cell/celleb_scc_pciex.c |   12 +---------
 arch/powerpc/platforms/chrp/pci.c              |    8 +++----
 arch/powerpc/platforms/iseries/pci.c           |    8 +++----
 arch/powerpc/platforms/powermac/setup.c        |    2 -
 arch/powerpc/platforms/pseries/setup.c         |   25 ++++++++++++++++++++++
 arch/powerpc/sysdev/fsl_pci.c                  |    6 ++---
 arch/powerpc/sysdev/indirect_pci.c             |    4 +--
 arch/powerpc/sysdev/ppc4xx_pci.c               |    4 +--
 arch/powerpc/sysdev/tsi108_pci.c               |    4 +--
 drivers/pci/Makefile                           |    1
 19 files changed, 57 insertions(+), 122 deletions(-)

Kumar Gala (13):
      powerpc/pci: clean up direct access to sysdata by indirect ops
      powerpc/pci: clean up direct access to sysdata by FSL platforms
      powerpc/pci: clean up direct access to sysdata by 52xx platforms
      powerpc/pci: clean up direct access to sysdata by 4xx platforms
      powerpc/pci: clean up direct access to sysdata by CHRP platforms
      powerpc/pci: clean up direct access to sysdata on tsi108 platforms
      powerpc/pci: clean up direct access to sysdata by powermac platforms
      powerpc/pci: clean up direct access to sysdata by RTAS
      powerpc/pci: clean up direct access to sysdata by celleb platforms
      powerpc/pci: clean up direct access to sysdata by iseries platform
      powerpc/pci: Move pseries code into pseries platform specific area
      powerpc/pci: cleanup some minor cruft
      powerpc/pci: Remove redundant pcnet32 fixup

                 reply	other threads:[~2009-05-05 12:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.0905050721500.18785@localhost.localdomain \
    --to=galak@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).