From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
tglx@linutronix.de, aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/riscv-intc: Fix use of AIA IRQs 32-63 on riscv32
Date: Mon, 25 Mar 2024 04:42:34 +0000 [thread overview]
Message-ID: <171134175473.18749.6561888891935488179.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240312212813.2323841-1-samuel.holland@sifive.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@linutronix.de>:
On Tue, 12 Mar 2024 14:28:08 -0700 you wrote:
> riscv_intc_custom_base is initialized to BITS_PER_LONG, so the second
> check passes even though AIA provides 64 IRQs. Adjust the condition to
> only check the custom IRQ range for IRQs outside the standard range, and
> adjust the standard range when AIA is available.
>
> Fixes: bb7921cdea12 ("irqchip/riscv-intc: Add support for RISC-V AIA")
> Fixes: e6bd9b966dc8 ("irqchip/riscv-intc: Fix low-level interrupt handler setup for AIA")
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
>
> [...]
Here is the summary with links:
- irqchip/riscv-intc: Fix use of AIA IRQs 32-63 on riscv32
https://git.kernel.org/riscv/c/ca5b0b717b75
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:[~2024-03-25 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 21:28 [PATCH] irqchip/riscv-intc: Fix use of AIA IRQs 32-63 on riscv32 Samuel Holland
2024-03-13 4:34 ` Anup Patel
2024-03-13 10:55 ` [tip: irq/urgent] irqchip/riscv-intc: Fix use of AIA interrupts " tip-bot2 for Samuel Holland
2024-03-15 18:54 ` tip-bot2 for Samuel Holland
2024-03-25 4:42 ` 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=171134175473.18749.6561888891935488179.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox