From: patchwork-bot+linux-riscv@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
saravanak@google.com, krzk+dt@kernel.org, conor+dt@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, samuel@sholland.org, maz@kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com, magnus.damm@gmail.com,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] of/irq: Ignore interrupt parent for nodes without interrupts
Date: Fri, 19 Dec 2025 08:10:13 +0000 [thread overview]
Message-ID: <176613181379.3684357.14380947909185500489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fbe6fc3657070fe2df7f0529043542b52b827449.1763116833.git.geert+renesas@glider.be>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Rob Herring (Arm) <robh@kernel.org>:
On Fri, 14 Nov 2025 11:47:54 +0100 you wrote:
> The Devicetree Specification states:
>
> The root of the interrupt tree is determined when traversal of the
> interrupt tree reaches an interrupt controller node without an
> interrupts property and thus no explicit interrupt parent.
>
> However, of_irq_init() gratuitously assumes that a node without
> interrupts has an actual interrupt parent if it finds an
> interrupt-parent property higher up in the device tree. Hence when such
> a property is present (e.g. in the root node), the root interrupt
> controller may not be detected as such, causing a panic:
>
> [...]
Here is the summary with links:
- [v2] of/irq: Ignore interrupt parent for nodes without interrupts
https://git.kernel.org/riscv/c/1b1f04d8271e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-12-19 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 10:47 Geert Uytterhoeven
2025-11-17 17:27 ` Rob Herring (Arm)
2025-11-18 19:34 ` Mark Brown
2025-11-18 19:55 ` Krzysztof Kozlowski
2025-11-19 8:53 ` Geert Uytterhoeven
2025-11-19 9:55 ` Marek Szyprowski
2025-11-19 10:59 ` Geert Uytterhoeven
2025-11-20 10:11 ` Jon Hunter
2025-11-28 16:42 ` Ioana Ciornei
2025-11-28 17:09 ` Ioana Ciornei
2025-12-01 12:09 ` Rob Herring
2025-12-01 12:50 ` Geert Uytterhoeven
2025-12-01 14:34 ` Rob Herring
2025-12-02 16:36 ` Ioana Ciornei
2025-12-02 21:19 ` Rob Herring
2025-12-03 9:48 ` Ioana Ciornei
2025-12-03 9:57 ` Geert Uytterhoeven
2025-12-03 14:55 ` Rob Herring
2025-12-19 8:10 ` patchwork-bot+linux-riscv [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=176613181379.3684357.14380947909185500489.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=saravanak@google.com \
/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
Powered by JetHome