linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@ozlabs.org
Subject: patches added to powerpc.git tree
Date: Fri, 7 Jul 2006 21:29:47 +1000	[thread overview]
Message-ID: <17582.17835.641485.233064@cargo.ozlabs.ibm.com> (raw)

The following patches have been pushed to the powerpc.git tree (master
branch):

Benjamin Herrenschmidt:
      [POWERPC] Workaround Pegasos incorrect ISA "ranges"
      [POWERPC] Fix 32 bits warning in prom_init.c
      [POWERPC] Fix non-MPIC CHRPs with CONFIG_SMP set
      [POWERPC] Fix default clock for udbg_16550
      [POWERPC] Fix legacy_serial.c error handling on 32 bits
      [POWERPC] Add briq support to CHRP
      [POWERPC] Add support for briq front panel
      [POWERPC] More offb/bootx fixes
      [POWERPC] Xserve G5 thermal control fixes
      [POWERPC] Add cpufreq support for Xserve G5

Jeremy Kerr:
      [POWERPC] Remove linux,device properties
      [POWERPC] Use const qualifiers for prom parsing utilites
      [POWERPC] Remove linux,pci-domain properties

Johannes Berg:
      [POWERPC] fix up front-LED Kconfig

Michael Ellerman:
      [POWERPC] Fix mem= handling when the memory limit is > RMO size

Niels Kristian Bech Jensen:
      [POWERPC] Add -fno-stack-protector to BOOTCFLAGS in arch/powerpc/boot/Makefile.

 arch/powerpc/Kconfig                         |    2 
 arch/powerpc/boot/Makefile                   |    4 
 arch/powerpc/configs/pmac32_defconfig        |  112 ++++++++-
 arch/powerpc/kernel/legacy_serial.c          |   13 +
 arch/powerpc/kernel/of_device.c              |   24 --
 arch/powerpc/kernel/pci_64.c                 |   39 ---
 arch/powerpc/kernel/prom_init.c              |   42 ++++
 arch/powerpc/kernel/prom_parse.c             |   22 +-
 arch/powerpc/kernel/smp.c                    |   24 +-
 arch/powerpc/kernel/udbg_16550.c             |    6 -
 arch/powerpc/mm/lmb.c                        |    3 
 arch/powerpc/platforms/chrp/pci.c            |   42 +++-
 arch/powerpc/platforms/chrp/setup.c          |   39 +++
 arch/powerpc/platforms/powermac/bootx_init.c |   35 ++-
 arch/powerpc/platforms/powermac/cpufreq_64.c |   78 ++++---
 drivers/char/Kconfig                         |   14 +
 drivers/char/Makefile                        |    1 
 drivers/char/briq_panel.c                    |  268 +++++++++++++++++++++++
 drivers/ide/Kconfig                          |   14 -
 drivers/macintosh/Kconfig                    |    9 +
 drivers/macintosh/therm_pm72.c               |  218 +++++++++++++++++-
 drivers/macintosh/therm_pm72.h               |   33 +++
 drivers/macintosh/via-pmu-led.c              |    2 
 drivers/video/offb.c                         |  307 ++++++++++++++------------
 include/asm-powerpc/processor.h              |    1 
 include/asm-powerpc/prom.h                   |    2 
 26 files changed, 1023 insertions(+), 331 deletions(-)
 create mode 100644 drivers/char/briq_panel.c

             reply	other threads:[~2006-07-07 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 11:29 Paul Mackerras [this message]
2006-07-07 11:39 ` patches added to powerpc.git tree Johannes Berg
2006-07-10 12:36   ` Paul Mackerras
2006-07-10 13:00     ` Johannes Berg
2006-07-10  3:05 ` 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=17582.17835.641485.233064@cargo.ozlabs.ibm.com \
    --to=paulus@samba.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).