devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms@verge.net.au>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 0/4] ARM: shmobile: dtsi: interrupt-parent cleanups
Date: Wed, 20 Aug 2014 23:53:05 +0900	[thread overview]
Message-ID: <CANqRtoTDdrR-VJ4dh96BJBmw5b-fHPRELNTrHTZK7jEXYasmJQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWFhqv5j8g8wGnaXBOZ7r7vBpOnW4K_KY7WAs04OYxQQg@mail.gmail.com>

On Wed, Aug 20, 2014 at 11:32 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Wed, Aug 20, 2014 at 4:28 PM, Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
>> This series cleans up interrupt-parent use, to match common use.
>> It makes sure there's an "interrupt-parent = <&gic>;" at the top, which is
>> thus inherited by all child nodes, and removes superflous "interrupt-parent"
>> properties from the individual child nodes.
>>
>> This was tested on r8a7791/koelsch only.
>>
>> Geert Uytterhoeven (4):
>>   ARM: shmobile: r8a7779 dtsi: Remove superfluous interrupt-parent
>>   ARM: shmobile: r8a7790 dtsi: Remove superfluous interrupt-parent
>>   ARM: shmobile: r8a7790 dtsi: Remove superfluous interrupt-parent
>
> Oops, that should have been "r8a7791". I've sent a fixed version of that patch.
>
>>   ARM: shmobile: sh73a0 dtsi: Move interrupt-parent to the top

Thanks, those look like fine cleanups to me!

Acked-by: Magnus Damm <damm+renesas@opensource.se>

I suppose both your and my recent patches need a bit of testing, so I
guess it may make sense for Simon to merge one series at a time to
avoid introducing multiple potential issues simultaneously... Combine
early delay issues with Kconfig errors and potential interrupt parent
error and you have something fun to debug. =)

/ magnus

  reply	other threads:[~2014-08-20 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 14:28 [PATCH 0/4] ARM: shmobile: dtsi: interrupt-parent cleanups Geert Uytterhoeven
     [not found] ` <1408544914-21742-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2014-08-20 14:28   ` [PATCH 1/4] ARM: shmobile: r8a7779 dtsi: Remove superfluous interrupt-parent Geert Uytterhoeven
2014-08-20 14:28 ` [PATCH 2/4] ARM: shmobile: r8a7790 " Geert Uytterhoeven
2014-08-20 14:28 ` [PATCH 3/4] " Geert Uytterhoeven
2014-08-20 14:28 ` [PATCH 4/4] ARM: shmobile: sh73a0 dtsi: Move interrupt-parent to the top Geert Uytterhoeven
2014-08-20 14:31 ` [PATCH 3/4] ARM: shmobile: r8a7791 dtsi: Remove superfluous interrupt-parent Geert Uytterhoeven
2014-08-20 14:32 ` [PATCH 0/4] ARM: shmobile: dtsi: interrupt-parent cleanups Geert Uytterhoeven
2014-08-20 14:53   ` Magnus Damm [this message]
2014-08-22  3:39     ` Simon Horman

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=CANqRtoTDdrR-VJ4dh96BJBmw5b-fHPRELNTrHTZK7jEXYasmJQ@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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).