All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Please pull 'next' branch of 5xxx tree
Date: Mon, 4 Nov 2013 01:11:23 +0100	[thread overview]
Message-ID: <20131104011123.31e8dfb2@crub> (raw)

Hi Ben !

Please pull mpc5xxx patches for v3.13:

Fixes for build issues when LPB FIFO driver is configured as
a module, removal of #ifdefs in mpc512x DIU platform code and
a revert of recent changes to mpc52xx PIC driver. Wolfram
provided a better fix for PIC driver build issue popping up
when older gcc-4.3.5 is used.

Thanks,
Anatolij
 
The following changes since commit 50bd6153d1a68354a0a0c8bca1fe949fa8875875:

  powerpc/powernv: Code update interface (2013-10-30 16:12:02 +1100)

are available in the git repository at:

  git://git.denx.de/linux-2.6-agust.git next

for you to fetch changes up to 7e198197ec878c720af4dc35c49c0c6a99b83f9f:

  powerpc/mpc512x: remove unnecessary #if (2013-10-30 22:56:10 +0100)

----------------------------------------------------------------
Anatolij Gustschin (1):
      powerpc/52xx: fix build breakage for MPC5200 LPBFIFO module

Brian Norris (1):
      powerpc/mpc512x: remove unnecessary #if

Gerhard Sittig (1):
      powerpc/mpc512x: silence build warning upon disabled DIU

Wolfram Sang (1):
      Kind of revert "powerpc: 52xx: provide a default in mpc52xx_irqhost_map()"

 arch/powerpc/platforms/512x/mpc512x_shared.c |   18 +++++++-----------
 arch/powerpc/platforms/52xx/Kconfig          |    2 +-
 arch/powerpc/platforms/52xx/mpc52xx_pic.c    |    5 ++---
 arch/powerpc/sysdev/fsl_soc.h                |    3 ---
 4 files changed, 10 insertions(+), 18 deletions(-)

             reply	other threads:[~2013-11-04  0:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  0:11 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-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-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=20131104011123.31e8dfb2@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 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.