From: Anatolij Gustschin <agust@denx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@ozlabs.org
Subject: Please pull 'next' branch of 5xxx tree
Date: Mon, 29 Apr 2013 11:42:50 +0200 [thread overview]
Message-ID: <20130429114250.1f4285c9@crub> (raw)
Hi Ben !
Please pull mpc5xxx patches for v3.10. There are some changes
for mpc5121 generic platform code to support mpc5125 SoC and DTS
files for ac14xx and MPC5125-TWR boards.
All these patches have already been in linux-next for a while.
Thanks,
Anatolij
The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository at:
git://git.denx.de/linux-2.6-agust.git next
for you to fetch changes up to fdeaf0e20e9f3999c5cb129e821595fe927bf259:
powerpc/512x: add ifm ac14xx board (2013-04-10 20:48:44 +0200)
----------------------------------------------------------------
Anatolij Gustschin (2):
powerpc/mpc512x: create SoC devices for more nodes
powerpc/512x: add ifm ac14xx board
Matteo Facchinetti (2):
powerpc/512x: move mpc5121_generic platform to mpc512x_generic.
powerpc/mpc512x: add platform code for MPC5125.
arch/powerpc/boot/dts/ac14xx.dts | 392 ++++++++++++++++++++
arch/powerpc/boot/dts/mpc5121.dtsi | 2 +-
arch/powerpc/boot/dts/mpc5121ads.dts | 2 +-
arch/powerpc/boot/dts/mpc5125twr.dts | 233 ++++++++++++
arch/powerpc/boot/dts/pdm360ng.dts | 2 +-
arch/powerpc/configs/mpc512x_defconfig | 2 +-
arch/powerpc/platforms/512x/Kconfig | 8 +-
arch/powerpc/platforms/512x/Makefile | 2 +-
arch/powerpc/platforms/512x/clock.c | 9 +-
arch/powerpc/platforms/512x/mpc512x.h | 1 +
.../512x/{mpc5121_generic.c => mpc512x_generic.c} | 12 +-
arch/powerpc/platforms/512x/mpc512x_shared.c | 33 +-
12 files changed, 674 insertions(+), 24 deletions(-)
create mode 100644 arch/powerpc/boot/dts/ac14xx.dts
create mode 100644 arch/powerpc/boot/dts/mpc5125twr.dts
rename arch/powerpc/platforms/512x/{mpc5121_generic.c => mpc512x_generic.c} (83%)
next reply other threads:[~2013-04-29 9:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 9:42 Anatolij Gustschin [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 21:18 Please pull 'next' branch of 5xxx tree 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
2013-11-04 0:11 Anatolij Gustschin
2013-09-03 20:39 Anatolij Gustschin
2013-09-05 6:50 ` Benjamin Herrenschmidt
2013-09-09 9:38 ` 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-02-19 23:57 Anatolij Gustschin
2012-12-11 8:23 Anatolij Gustschin
2012-09-24 14:45 Anatolij Gustschin
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
2011-09-30 6:31 Heiko Schocher
2011-09-30 6:38 ` Heiko Schocher
2011-09-29 9:30 Anatolij Gustschin
2011-09-29 12:49 ` Grant Likely
2011-09-22 23:20 Anatolij Gustschin
2011-09-23 0:15 ` 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=20130429114250.1f4285c9@crub \
--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 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).