From: patchwork-bot+linux-riscv@kernel.org
To: Yangyu Chen <cyy@cyyself.name>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
anup.patel@oss.qualcomm.com, samuel.holland@sifive.com,
cmirabil@redhat.com, lzampier@redhat.com, tglx@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, mason.huo@starfivetech.com,
zhangxincheng@ultrarisc.com, charlie@rivosinc.com,
maz@kernel.org, jeeheng.sia@starfivetech.com,
leyfoon.tan@starfivetech.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, alex@ghiti.fr,
devicetree@vger.kernel.org, yash.shah@sifive.com,
wangjia@ultrarisc.com
Subject: Re: [PATCH v3 0/2] irqchip/sifive-plic: Fix wrong nr_irqs handling
Date: Fri, 20 Feb 2026 04:10:50 +0000 [thread overview]
Message-ID: <177156065079.189817.10993105171560022947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_AEBB719FAF49D05B5BDF7118D729463F6405@qq.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@kernel.org>:
On Wed, 4 Feb 2026 01:17:07 +0800 you wrote:
> This patch series fixes long standing bugs in sifive-plic driver regarding
> the handling of nr_irqs. Some code assumes the first irq source is 0 while
> some assumes it is 1. Since the first irq source is actually 1, this causes
> various issues including memory corruption when the number of irqs is
> multiple of 32. Also, some code assumes nr_irqs is the maximum irq source
> ID while some assumes it is the total number of irq sources including the
> reserved source 0. This patch series standardizes the handling of nr_irqs
> to be the maximum irq source ID, and the first irq source is 1.
>
> [...]
Here is the summary with links:
- [v3,1/2] irqchip/sifive-plic: Fix wrong nr_irqs handling
(no matching commit)
- [v3,2/2] dt-binding: riscv: Clarify the riscv,ndev meaning in PLIC
https://git.kernel.org/riscv/c/889588d75050
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-02-20 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:17 [PATCH v3 0/2] irqchip/sifive-plic: Fix wrong nr_irqs handling Yangyu Chen
2026-02-03 17:21 ` [PATCH v3 1/2] " Yangyu Chen
2026-02-03 20:40 ` Thomas Gleixner
2026-02-04 4:40 ` Yangyu Chen
2026-02-04 17:46 ` Conor Dooley
2026-02-03 17:21 ` [PATCH v3 2/2] dt-binding: riscv: Clarify the riscv,ndev meaning in PLIC Yangyu Chen
2026-02-04 17:49 ` Conor Dooley
2026-02-20 4: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=177156065079.189817.10993105171560022947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup.patel@oss.qualcomm.com \
--cc=charlie@rivosinc.com \
--cc=cmirabil@redhat.com \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=jeeheng.sia@starfivetech.com \
--cc=krzk+dt@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lzampier@redhat.com \
--cc=mason.huo@starfivetech.com \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@kernel.org \
--cc=wangjia@ultrarisc.com \
--cc=yash.shah@sifive.com \
--cc=zhangxincheng@ultrarisc.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