From: Sekhar Nori <nsekhar@ti.com>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: LAK <linux-arm-kernel@lists.infradead.org>,
DLOS <davinci-linux-open-source@linux.davincidsp.com>,
LKML <linux-kernel@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
"Lad, Prabhakar" <prabhakar.lad@ti.com>,
devicetree-discuss@lists.ozlabs.org, Heiko Schocher <hs@denx.de>
Subject: Re: [PATCH] ARM: davinci: da850: add interrupt-parent property in soc node
Date: Mon, 28 Jan 2013 21:03:14 +0530 [thread overview]
Message-ID: <51069A3A.8090404@ti.com> (raw)
In-Reply-To: <1359112724-1217-1-git-send-email-prabhakar.lad@ti.com>
On 1/25/2013 4:48 PM, Prabhakar Lad wrote:
> From: Lad, Prabhakar <prabhakar.lad@ti.com>
>
> This patch adds 'interrupt-parent' property in soc node, so that
> the child inherits this property, this avoids adding 'interrupt-parent'
> to each node.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.lad@ti.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Cc: devicetree-discuss@lists.ozlabs.org
> Cc: Sekhar Nori <nsekhar@ti.com>
> Cc: Heiko Schocher <hs@denx.de>
> ---
Looks good to me. Queuing for v3.9. BTW, we are moving the interrupt
parent property to soc node rather than adding it. So, I think a better
headline is "move interrupt-parent property to soc node". I change the
headline while committing.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-01-28 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 11:18 [PATCH] ARM: davinci: da850: add interrupt-parent property in soc node Prabhakar Lad
2013-01-28 15:33 ` Sekhar Nori [this message]
2013-01-28 16:11 ` Prabhakar Lad
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=51069A3A.8090404@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hs@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.lad@ti.com \
/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).