public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] ARM: mvebu: dt changes for v3.11 (round 6!)
Date: Fri, 21 Jun 2013 19:58:00 +0200	[thread overview]
Message-ID: <201306211958.00637.arnd@arndb.de> (raw)
In-Reply-To: <20130621164611.GT31667@titan.lakedaemon.net>

On Friday 21 June 2013, Jason Cooper wrote:
> Arnd, Olof,
> 
> Here's the last stragglers for v3.11.  Nothing too traumatic :)
> 
> This does cause a merge conflict in kirkwood.dtsi with my
> mvebu/pcie_kirkwood branch.  The resolution is to keep the changes in
> this branch.
> 
> 
> The following changes since commit 918f8f309643978b9e761f39af8962a7388d332d:
> 
>   ARM: Kirkwood: ts219: Enable second PCIe port in DT. (2013-06-11 16:02:08 +0000)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/users/jcooper/linux.git tags/dt-3.11-6
> 
> for you to fetch changes up to 01db527e657d6cf646c6e6f059ad41e7023a25e7:
> 
>   ARM: Kirkwood: Fix the internal register ranges translation (2013-06-21 15:38:20 +0000)
> 
> ----------------------------------------------------------------
> mvebu dt changes for v3.11 (round 6)
> 
>  - mvebu
>     - mini-PCIe connectors on Armada 370 RD
> 
>  - kirkwood
>     - correct internal register ranges translation
> 
> ----------------------------------------------------------------
> Ezequiel Garcia (1):
>       ARM: Kirkwood: Fix the internal register ranges translation
> 
> Thomas Petazzoni (1):
>       arm: mvebu: enable mini-PCIe connectors on Armada 370 RD
> 
>  arch/arm/boot/dts/armada-370-rd.dts | 16 ++++++++++++++++
>  arch/arm/boot/dts/kirkwood.dtsi     |  5 +++--
>  2 files changed, 19 insertions(+), 2 deletions(-)
> 

Pulled into next/dt, thanks!

I got a non-obvious conflict that I resolved like this:


--- a/arch/arm/boot/dts/kirkwood.dtsi
+++ b/arch/arm/boot/dts/kirkwood.dtsi
@@@ -30,8 -30,8 +30,9 @@@
  
        ocp at f1000000 {
                compatible = "simple-bus";
-               ranges = <0x00000000 0xf1000000 0x4000000
+               ranges = <0x00000000 0xf1000000 0x0100000
 +                        0xe0000000 0xe0000000 0x8100000 /* PCIE */
+                         0xf4000000 0xf4000000 0x0000400
                          0xf5000000 0xf5000000 0x0000400>;
                #address-cells = <1>;
                #size-cells = <1>;


	Arnd

  reply	other threads:[~2013-06-21 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 16:46 [GIT PULL 1/2] ARM: mvebu: dt changes for v3.11 (round 6!) Jason Cooper
2013-06-21 17:58 ` Arnd Bergmann [this message]
2013-06-21 18:14   ` Ezequiel Garcia
2013-06-21 18:25   ` Jason Cooper

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=201306211958.00637.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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