From: patchwork-bot+linux-riscv@kernel.org
To: Charles Mirabile <cmirabil@redhat.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
lzampier@redhat.com, samuel.holland@sifive.com, pjw@kernel.org,
tglx@linutronix.de, lkp@intel.com
Subject: Re: [PATCH] irqchip/sifive-plic: fix call to __plic_toggle in M-Mode code path
Date: Fri, 19 Dec 2025 08:10:04 +0000 [thread overview]
Message-ID: <176613180427.3684357.14207836014506509623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251103161813.2437427-1-cmirabil@redhat.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@linutronix.de>:
On Mon, 3 Nov 2025 11:18:13 -0500 you wrote:
> The code path for M-Mode linux that disables interrupts for other contexts
> was missed when refactoring __plic_toggle.
>
> Since the new version caches updates to the state for the primary context,
> its use in this codepath is no longer desireable even if it could be made
> correct.
>
> [...]
Here is the summary with links:
- irqchip/sifive-plic: fix call to __plic_toggle in M-Mode code path
https://git.kernel.org/riscv/c/a045359e7245
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
prev parent reply other threads:[~2025-12-19 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 16:18 [PATCH] irqchip/sifive-plic: fix call to __plic_toggle in M-Mode code path Charles Mirabile
2025-12-19 8: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=176613180427.3684357.14207836014506509623.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=cmirabil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=lzampier@redhat.com \
--cc=pjw@kernel.org \
--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