From: Lars-Peter Clausen <lars@metafoo.de>
To: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 31/36] devicetree: document ingenic,jz4780-intc binding
Date: Sun, 25 Jan 2015 19:15:00 +0100 [thread overview]
Message-ID: <54C532A4.4090107@metafoo.de> (raw)
In-Reply-To: <1421620945-25502-1-git-send-email-paul.burton@imgtec.com>
On 01/18/2015 11:42 PM, Paul Burton wrote:
[...]
> +Ingenic jz4780 SoC Interrupt Controller
> +
> +Required properties:
> +
> +- compatible : should be "ingenic,jz4780-intc"
I don't think we need a second binding specification. Just add the
compatibility string to the existing jz4740-intc specification.
prev parent reply other threads:[~2015-01-25 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1421620067-23933-1-git-send-email-paul.burton@imgtec.com>
[not found] ` <1421620067-23933-1-git-send-email-paul.burton-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-01-18 22:27 ` [PATCH 01/36] devicetree/bindings: add Ingenic Semiconductor vendor prefix Paul Burton
2015-01-18 22:27 ` [PATCH 07/36] devicetree: document ingenic,jz4740-intc binding Paul Burton
[not found] ` <1421620067-23933-8-git-send-email-paul.burton-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-01-19 11:54 ` Sergei Shtylyov
2015-01-18 22:27 ` [PATCH 15/36] devicetree: add ingenic,jz4740-cgu binding documentation Paul Burton
2015-01-18 22:40 ` [PATCH 24/36] devicetree: document ingenic,jz4740-uart binding Paul Burton
2015-01-18 22:41 ` [PATCH 25/36] devicetree: document ingenic,jz4780-uart binding Paul Burton
[not found] ` <1421620869-25063-1-git-send-email-paul.burton-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-01-25 18:17 ` Lars-Peter Clausen
2015-01-18 22:41 ` [PATCH 29/36] devicetree: add ingenic,jz4780-cgu binding documentation Paul Burton
2015-01-18 22:42 ` [PATCH 31/36] devicetree: document ingenic,jz4780-intc binding Paul Burton
2015-01-19 12:08 ` Sergei Shtylyov
2015-01-25 18:15 ` Lars-Peter Clausen [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=54C532A4.4090107@metafoo.de \
--to=lars@metafoo.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.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).