From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: dts: Move interrupt-parent property to root node
Date: Wed, 30 Apr 2014 08:05:16 +0000 [thread overview]
Message-ID: <20140430080516.GA4378@katana> (raw)
In-Reply-To: <1398818488-6591-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
On Wed, Apr 30, 2014 at 02:41:28AM +0200, Laurent Pinchart wrote:
> There's no need to duplicate the interrupt-parent property in all DT
> nodes as the kernel automatically walks parent nodes to find the
> property. Specify it once in the root node only.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-30 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 0:41 [PATCH] ARM: shmobile: dts: Move interrupt-parent property to root node Laurent Pinchart
2014-04-30 8:05 ` Wolfram Sang [this message]
2014-05-12 23:37 ` Laurent Pinchart
2014-05-13 1:13 ` 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=20140430080516.GA4378@katana \
--to=wsa@the-dreams.de \
--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).