From: patchwork-bot+linux-riscv@kernel.org
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-riscv@lists.infradead.org, alexghiti@rivosinc.com,
anup@brainfault.org, linux-kernel@vger.kernel.org,
palmer@dabbelt.com, paul.walmsley@sifive.com, helgaas@kernel.org
Subject: Re: [Patch] PCI/MSI: Handle lack of irqdomain gracefully
Date: Mon, 03 Feb 2025 19:16:05 +0000 [thread overview]
Message-ID: <173861016523.3409359.17144106857280906043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <87ed2a8ow5.ffs@tglx>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@linutronix.de>:
On Sat, 14 Dec 2024 12:50:18 +0100 you wrote:
> Alexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a
> RISCV platform which does not provide PCI/MSI support:
>
> WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32
> __pci_enable_msix_range+0x30c/0x596
> pci_msi_setup_msi_irqs+0x2c/0x32
> pci_alloc_irq_vectors_affinity+0xb8/0xe2
>
> [...]
Here is the summary with links:
- PCI/MSI: Handle lack of irqdomain gracefully
https://git.kernel.org/riscv/c/a60b990798eb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-02-03 21:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 11:57 [RFC PATCH] riscv: Fix PCI warning by enabling PCI_MSI_ARCH_FALLBACKS Alexandre Ghiti
2024-12-13 13:12 ` Thomas Gleixner
2024-12-13 13:51 ` Alexandre Ghiti
2024-12-14 11:50 ` [Patch] PCI/MSI: Handle lack of irqdomain gracefully Thomas Gleixner
2024-12-17 13:08 ` [tip: irq/urgent] " tip-bot2 for Thomas Gleixner
2025-02-03 19:16 ` patchwork-bot+linux-riscv [this message]
2026-03-11 11:22 ` [Patch] " Uwe Kleine-König
2026-03-11 11:22 ` Uwe Kleine-König
2026-04-22 8:50 ` Thorsten Leemhuis
2026-04-22 8:50 ` Thorsten Leemhuis
2026-04-22 15:07 ` Aaron D. Johnson
2026-04-22 15:07 ` Aaron D. Johnson
2026-04-22 19:52 ` Thomas Gleixner
2026-04-22 19:52 ` Thomas Gleixner
2026-04-22 21:22 ` Thomas Gleixner
2026-04-22 21:22 ` Thomas Gleixner
2026-04-22 22:34 ` Aaron D. Johnson
2026-04-22 22:34 ` Aaron D. Johnson
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=173861016523.3409359.17144106857280906043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.