From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anatolij Gustschin <agust@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull 'next' branch of 5xxx tree
Date: Tue, 02 Jul 2013 17:46:01 +1000 [thread overview]
Message-ID: <1372751161.3616.1.camel@pasglop> (raw)
In-Reply-To: <20130702003605.2838c666@crub>
On Tue, 2013-07-02 at 00:36 +0200, Anatolij Gustschin wrote:
> Hi Ben !
>
> Please pull mpc5xxx patches for v3.11. There are small cleanups
> and fixes for mpc512x common code, mpc512x_defconfig updates and
> soft reboot support for mpc5125 based boards.
Looks like your server is down...
Cheers,
Ben.
> Thanks,
>
> Anatolij
>
> The following changes since commit c7788792a5e7b0d5d7f96d0766b4cb6112d47d75:
>
> Linux 3.10-rc2 (2013-05-20 14:37:38 -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 dd0120dea601de654a5a6d959da3a632a02200f0:
>
> powerpc/mpc512x: enable USB support in defconfig (2013-06-25 08:51:19 +0200)
>
> ----------------------------------------------------------------
> Anatolij Gustschin (1):
> powerpc/mpc512x: enable USB support in defconfig
>
> Gerhard Sittig (3):
> powerpc/mpc512x: move common code to shared.c file
> powerpc/mpc512x: initialize board restart earlier
> powerpc/mpc512x: commit re-generated defconfig
>
> Matteo Facchinetti (1):
> powerpc/mpc512x: add MPC5125 reset module support for system restart
>
> arch/powerpc/configs/mpc512x_defconfig | 27 ++++++++-------------
> arch/powerpc/include/asm/mpc5121.h | 1 -
> arch/powerpc/platforms/512x/mpc5121_ads.c | 6 ++---
> arch/powerpc/platforms/512x/mpc512x.h | 12 +++-------
> arch/powerpc/platforms/512x/mpc512x_generic.c | 4 ++--
> arch/powerpc/platforms/512x/mpc512x_shared.c | 31 ++++++++++++++++++++++---
> arch/powerpc/platforms/512x/pdm360ng.c | 4 ++--
> 7 files changed, 47 insertions(+), 38 deletions(-)
next prev parent reply other threads:[~2013-07-02 7:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 22:36 Please pull 'next' branch of 5xxx tree Anatolij Gustschin
2013-07-02 7:46 ` Benjamin Herrenschmidt [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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-04-29 9:42 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=1372751161.3616.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agust@denx.de \
--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).