From: patchwork-bot+linux-riscv@kernel.org
To: <liu.xuemei1@zte.com.cn>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
tglx@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, nick.hu@sifive.com,
liujingqi@lanxincomputing.com, yongxuan.wang@sifive.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/riscv-aplic: Restrict genpd notifier to device tree only
Date: Thu, 30 Apr 2026 03:25:06 +0000 [thread overview]
Message-ID: <177751950629.2274119.11651401425571807899.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260331093029749vRpdH-0qoEqjS0Wnn9M4x@zte.com.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@kernel.org>:
On Tue, 31 Mar 2026 09:30:29 +0800 (CST) you wrote:
> From: Jessica Liu <liu.xuemei1@zte.com.cn>
>
> On ACPI systems, the aplic's pm_domain is set to
> acpi_general_pm_domain, which provides its own power management
> callbacks (e.g., runtime_suspend via acpi_subsys_runtime_suspend).
> The aplic_pm_add() unconditionally calls dev_pm_genpd_add_notifier()
> when dev->pm_domain is non‑NULL, leading to a comparison between
> runtime_suspend and genpd_runtime_suspend. This results in the
> following errors when ACPI is enabled:
>
> [...]
Here is the summary with links:
- irqchip/riscv-aplic: Restrict genpd notifier to device tree only
https://git.kernel.org/riscv/c/af416cd9b3fb
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:[~2026-04-30 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 1:30 [PATCH] irqchip/riscv-aplic: Restrict genpd notifier to device tree only liu.xuemei1
2026-03-31 8:13 ` [tip: irq/urgent] " tip-bot2 for Jessica Liu
2026-04-30 3:25 ` 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=177751950629.2274119.11651401425571807899.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liu.xuemei1@zte.com.cn \
--cc=liujingqi@lanxincomputing.com \
--cc=nick.hu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tglx@kernel.org \
--cc=yongxuan.wang@sifive.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