From: patchwork-bot+linux-riscv@kernel.org
To: Thomas Gleixner <tglx@kernel.org>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
yingjun.ni@riscv-computing.com, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-kernel@vger.kernel.org, maz@kernel.org
Subject: Re: [PATCH] irqchip/msi-lib: Refuse initialization when irq_write_msi_msg() is missing
Date: Thu, 30 Apr 2026 03:26:03 +0000 [thread overview]
Message-ID: <177751956329.2274119.1202554287518338365.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <87a4xp35cn.ffs@tglx>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@kernel.org>:
On Tue, 03 Feb 2026 22:05:44 +0100 you wrote:
> MSI parent domains rely on the fact that the top level device domain
> provides a irq_write_msi_msg() callback.
>
> Check for that and if missing warn and refuse to initialize the device domain.
>
> Signed-off-by: Thomas Gleixner <tglx@kernel.org>
>
> [...]
Here is the summary with links:
- irqchip/msi-lib: Refuse initialization when irq_write_msi_msg() is missing
https://git.kernel.org/riscv/c/aa80869b77e1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-04-30 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 8:02 [PATCH] irqchip/riscv-imsic: Fix irq migration failure issue when cpu hotplug Yingjun Ni
2026-02-03 13:35 ` Thomas Gleixner
2026-02-03 17:09 ` Anup Patel
2026-02-03 18:28 ` Thomas Gleixner
2026-02-03 21:05 ` [PATCH] irqchip/msi-lib: Refuse initialization when irq_write_msi_msg() is missing Thomas Gleixner
2026-02-24 7:20 ` [tip: irq/msi] " tip-bot2 for Thomas Gleixner
2026-04-30 3:26 ` patchwork-bot+linux-riscv [this message]
2026-02-04 1:59 ` [PATCH] irqchip/riscv-imsic: Fix irq migration failure issue when cpu hotplug Yingjun Ni
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=177751956329.2274119.1202554287518338365.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=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tglx@kernel.org \
--cc=yingjun.ni@riscv-computing.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