From: Rob Herring <robh@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Alexandru M Stan <amstan@chromium.org>
Subject: Re: [PATCH] dt-bindings: Clarify interrupts-extended usage
Date: Thu, 29 Aug 2019 17:57:40 -0500 [thread overview]
Message-ID: <20190829225740.GA22740@bogus> (raw)
In-Reply-To: <20190827025511.22166-1-swboyd@chromium.org>
On Mon, 26 Aug 2019 19:55:11 -0700, Stephen Boyd wrote:
> Reading the description about when to use interrupts-extended leads some
> developers to think that it shouldn't be used unless a device has
> interrupts from more than one interrupt controller. This isn't true. We
> should encourage devicetree writers to use this property in situations
> where it isn't the inherited interrupt-parent so that we have less
> properties in a DT node by virtue of not having to specify an
> interrupt-parent and an interrupts property.
>
> Reported-by: Alexandru M Stan <amstan@chromium.org>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> .../bindings/interrupt-controller/interrupts.txt | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Applied, thanks.
Rob
prev parent reply other threads:[~2019-08-29 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 2:55 [PATCH] dt-bindings: Clarify interrupts-extended usage Stephen Boyd
2019-08-29 22:57 ` Rob Herring [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=20190829225740.GA22740@bogus \
--to=robh@kernel.org \
--cc=amstan@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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