linux-kernel - Re: [PATCH] MIPS: dts: lantiq: Remove bogus interrupt-parent; line

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: <20230205160301.GC4459@alpha.franken.de>
Date:   Sun, 5 Feb 2023 17:03:01 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Jonathan Neuschäfer <j.neuschaefer@....net>
Cc:     linux-mips@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: dts: lantiq: Remove bogus interrupt-parent; line

On Sun, Jan 29, 2023 at 04:20:58PM +0100, Jonathan Neuschäfer wrote:
> Specifying interrupt-parent without a value (in other words, as a bool)
> doesn't really mean anything. Remove one such property in the Lantiq
> Danube DT, at /sram@...00000/eiu@...000.
> 
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@....net>
> ---
>  arch/mips/boot/dts/lantiq/danube.dtsi | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/mips/boot/dts/lantiq/danube.dtsi b/arch/mips/boot/dts/lantiq/danube.dtsi
> index 510be63c8bdf1..7a7ba66aa5349 100644
> --- a/arch/mips/boot/dts/lantiq/danube.dtsi
> +++ b/arch/mips/boot/dts/lantiq/danube.dtsi
> @@ -40,7 +40,6 @@ sram@...00000 {
>  		eiu0: eiu@...000 {
>  			#interrupt-cells = <1>;
>  			interrupt-controller;
> -			interrupt-parent;
>  			compatible = "lantiq,eiu-xway";
>  			reg = <0x101000 0x1000>;
>  		};
> --
> 2.39.0

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]