All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, tglx@kernel.org, pjw@kernel.org,
	samuel.holland@sifive.com, maz@kernel.org, anup@brainfault.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/sifive-plic: Fix frozen interrupt due to affinity setting
Date: Tue, 24 Mar 2026 06:07:24 +0000	[thread overview]
Message-ID: <177433244498.469836.5203107878440214495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260212114125.3148067-1-namcao@linutronix.de>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Thomas Gleixner <tglx@kernel.org>:

On Thu, 12 Feb 2026 12:41:25 +0100 you wrote:
> PLIC ignores interrupt completion message for disabled interrupt, explained
> by the specification:
> 
>     The PLIC signals it has completed executing an interrupt handler by
>     writing the interrupt ID it received from the claim to the
>     claim/complete register. The PLIC does not check whether the completion
>     ID is the same as the last claim ID for that target. If the completion
>     ID does not match an interrupt source that is currently enabled for
>     the target, the completion is silently ignored.
> 
> [...]

Here is the summary with links:
  - irqchip/sifive-plic: Fix frozen interrupt due to affinity setting
    https://git.kernel.org/riscv/c/1072020685f4

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

      reply	other threads:[~2026-03-24  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 11:41 [PATCH] irqchip/sifive-plic: Fix frozen interrupt due to affinity setting Nam Cao
2026-03-24  6:07 ` 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=177433244498.469836.5203107878440214495.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=anup@brainfault.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=namcao@linutronix.de \
    --cc=pjw@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@kernel.org \
    /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.