From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 2/6] arm: dts: Fix dtc interrupt_provider warnings
Date: Tue, 13 Feb 2024 22:45:36 -0000 [thread overview]
Message-ID: <9a67cee101e7e15d5e70553e3929ee2fbd480c1f.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240213-arm-dt-cleanups-v1-2-f2dee1292525@kernel.org>
On Tue, 2024-02-13 at 13:34 -0600, Rob Herring wrote:
> The dtc interrupt_provider warning is off by default. Fix all the warnings
> so it can be enabled.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> arch/arm/boot/dts/amazon/alpine.dtsi | 1 -
> arch/arm/boot/dts/aspeed/aspeed-g4.dtsi | 14 --------------
> arch/arm/boot/dts/aspeed/aspeed-g5.dtsi | 15 +--------------
> arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 18 ++----------------
I wrote a very similar patch just a day or so ago, so thanks :)
For the Aspeed portions:
Reviewed-by: Andrew Jeffery <andrew@codeconstruct.com.au>
next prev parent reply other threads:[~2024-02-13 22:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 19:35 [PATCH 0/6] dts: Fix dtc interrupt warnings Rob Herring
2024-02-13 19:35 ` [PATCH 1/6] arm64: dts: freescale: Disable interrupt_map check Rob Herring
2024-02-13 19:35 ` [PATCH 2/6] arm: dts: Fix dtc interrupt_provider warnings Rob Herring
2024-02-13 22:45 ` Andrew Jeffery [this message]
2024-02-14 13:53 ` Alexandre TORGUE
2024-02-14 18:41 ` Florian Fainelli
2024-02-16 11:00 ` Thierry Reding
2024-02-13 19:35 ` [PATCH 3/6] arm64: " Rob Herring
2024-02-14 9:50 ` AngeloGioacchino Del Regno
2024-02-14 14:36 ` Geert Uytterhoeven
2024-02-14 18:41 ` Florian Fainelli
2024-02-15 9:25 ` Chanho Min
2024-02-13 19:35 ` [PATCH 4/6] arm: dts: Fix dtc interrupt_map warnings Rob Herring
2024-02-13 21:47 ` Linus Walleij
2024-02-13 19:35 ` [PATCH 5/6] arm64: dts: qcom: Fix interrupt-map cell sizes Rob Herring
2024-02-13 19:35 ` [PATCH 6/6] dtc: Enable dtc interrupt_provider check Rob Herring
2024-02-13 20:27 ` [PATCH 0/6] dts: Fix dtc interrupt warnings Conor Dooley
2024-02-13 20:56 ` Rob Herring
2024-02-14 15:01 ` Geert Uytterhoeven
2024-02-14 15:31 ` Rob Herring
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=9a67cee101e7e15d5e70553e3929ee2fbd480c1f.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).