mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-mips@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: dts: lantiq: Remove bogus interrupt-parent; line
Date: Sun, 5 Feb 2023 17:03:01 +0100	[thread overview]
Message-ID: <20230205160301.GC4459@alpha.franken.de> (raw)
In-Reply-To: <20230129152059.1535947-1-j.neuschaefer@gmx.net>

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@1f000000/eiu@101000.
> 
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.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@1f000000 {
>  		eiu0: eiu@101000 {
>  			#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 ]

      reply	other threads:[~2023-02-05 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 15:20 Jonathan Neuschäfer
2023-02-05 16:03 ` Thomas Bogendoerfer [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=20230205160301.GC4459@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=devicetree@vger.kernel.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh+dt@kernel.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

all inboxes | Powered by JetHome®