LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/85xx: Fix MPC8536DS 36-bit device tree
Date: Thu, 11 Apr 2013 08:34:14 -0500	[thread overview]
Message-ID: <4AF22D28-FA1A-4D09-94E1-9AF8AF175991@kernel.crashing.org> (raw)
In-Reply-To: <20130410165828.ec0378afc7e7f17e8e47850e@freescale.com>


On Apr 10, 2013, at 4:58 PM, Kim Phillips wrote:

> From: Kumar Gala <galak@kernel.crashing.org>
> 
> The localbus node should be in at 0xfffe05000 not 0xffe05000.  Also
> fixed the names of the localbus and pci nodes to reflect the addresses
> they are actually at.
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> ---
> note: this upstream submission extended to fix pci1.
> 
> arch/powerpc/boot/dts/mpc8536ds_36b.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)

applied to next

- k

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 21:58 [PATCH] powerpc/85xx: Fix MPC8536DS 36-bit device tree Kim Phillips
2013-04-11 13:34 ` Kumar Gala [this message]

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=4AF22D28-FA1A-4D09-94E1-9AF8AF175991@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=kim.phillips@freescale.com \
    --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