From: Anatolij Gustschin <agust@denx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Please pull 'next' branch of 5xxx tree
Date: Fri, 23 Sep 2011 01:20:00 +0200 [thread overview]
Message-ID: <20110923012000.31d4e38d@wker> (raw)
Hi Ben,
please pull some mpc5xxx updates and mpc8xxx/512x gpio driver
move patches for next.
Anatolij
The following changes since commit a120db06c3f435c37d028b6e5a1968dad06b7df0:
perf events, powerpc: Add POWER7 stalled-cycles-frontend/backend events (2011-09-20 16:12:56 +1000)
are available in the git repository at:
git://git.denx.de/linux-2.6-agust.git next
Anatolij Gustschin (4):
powerpc/5200: mpc5200b.dtsi: add spi node address- and size-cells properties
powerpc/5200: dts: digsy_mtc.dts: update to add can, pci, serial and spi
powerpc/5200: dts: digsy_mtc.dts: add timer0 and timer1 gpio properties
powerpc/5200: dts: digsy_mtc.dts: enable both MSCAN nodes
Timur Tabi (1):
powerpc/5200: enable audio in the defconfig
Wolfram Sang (2):
gpio: move mpc8xxx/512x gpio driver to drivers/gpio
powerpc: update 512x-defconfig
arch/powerpc/boot/dts/digsy_mtc.dts | 59 +++++++++++++++++---
arch/powerpc/boot/dts/mpc5200b.dtsi | 2 +
arch/powerpc/configs/85xx/p1023rds_defconfig | 2 +-
arch/powerpc/configs/85xx/xes_mpc85xx_defconfig | 2 +-
arch/powerpc/configs/mpc512x_defconfig | 19 ++++---
arch/powerpc/configs/mpc5200_defconfig | 12 ++++
arch/powerpc/configs/mpc85xx_defconfig | 2 +-
arch/powerpc/configs/mpc85xx_smp_defconfig | 2 +-
arch/powerpc/configs/ppc6xx_defconfig | 2 +-
arch/powerpc/platforms/512x/Kconfig | 1 +
arch/powerpc/platforms/83xx/Kconfig | 9 ++-
arch/powerpc/platforms/85xx/Kconfig | 12 +++-
arch/powerpc/platforms/86xx/Kconfig | 1 +
arch/powerpc/platforms/Kconfig | 10 ---
arch/powerpc/sysdev/Makefile | 1 -
drivers/gpio/Kconfig | 8 +++
drivers/gpio/Makefile | 1 +
.../mpc8xxx_gpio.c => drivers/gpio/gpio-mpc8xxx.c | 0
18 files changed, 106 insertions(+), 39 deletions(-)
rename arch/powerpc/sysdev/mpc8xxx_gpio.c => drivers/gpio/gpio-mpc8xxx.c (100%)
next reply other threads:[~2011-09-22 23:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 23:20 Anatolij Gustschin [this message]
2011-09-23 0:15 ` Please pull 'next' branch of 5xxx tree Benjamin Herrenschmidt
2011-09-29 9:30 Anatolij Gustschin
2011-09-29 12:49 ` Grant Likely
2011-09-30 6:31 Heiko Schocher
2011-09-30 6:38 ` Heiko Schocher
2012-03-20 17:04 Anatolij Gustschin
2012-03-20 22:30 ` Wolfram Sang
2012-03-20 23:32 ` Benjamin Herrenschmidt
2012-03-21 0:18 ` Anatolij Gustschin
2012-03-21 14:08 ` Stephen Rothwell
2012-03-21 0:56 ` Anatolij Gustschin
2012-09-24 14:45 Anatolij Gustschin
2012-12-11 8:23 Anatolij Gustschin
2013-02-19 23:57 Anatolij Gustschin
2013-04-29 9:42 Anatolij Gustschin
2013-07-01 22:36 Anatolij Gustschin
2013-07-02 7:46 ` Benjamin Herrenschmidt
2013-07-02 8:00 ` Anatolij Gustschin
2013-07-02 8:29 ` Benjamin Herrenschmidt
2013-07-02 10:29 ` Benjamin Herrenschmidt
2013-07-02 10:35 ` Anatolij Gustschin
2013-09-03 20:39 Anatolij Gustschin
2013-09-05 6:50 ` Benjamin Herrenschmidt
2013-09-09 9:38 ` Anatolij Gustschin
2013-11-04 0:11 Anatolij Gustschin
2014-01-15 21:18 Anatolij Gustschin
2014-01-28 5:46 ` Anatolij Gustschin
2014-01-28 6:00 ` Benjamin Herrenschmidt
2014-01-28 6:22 ` Anatolij Gustschin
2014-01-29 7:46 ` Benjamin Herrenschmidt
2014-01-29 10:11 ` Gerhard Sittig
2014-01-29 20:50 ` Anatolij Gustschin
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=20110923012000.31d4e38d@wker \
--to=agust@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.