linux-kernel - Re: [PATCH] dt-bindings: Clarify interrupts-extended usage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190829225740.GA22740@bogus>
Date:   Thu, 29 Aug 2019 17:57:40 -0500
From:   Rob Herring <robh@...nel.org>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     Frank Rowand <frowand.list@...il.com>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        Alexandru M Stan <amstan@...omium.org>
Subject: Re: [PATCH] dt-bindings: Clarify interrupts-extended usage

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@...omium.org>
> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
> ---
>  .../bindings/interrupt-controller/interrupts.txt          | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 

Applied, thanks.

Rob