From: Thomas Gleixner <tglx@linutronix.de>
To: patchwork-bot+linux-riscv@kernel.org,
Andrew Bresticker <abrestic@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
palmer@dabbelt.com, alex@ghiti.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/riscv-imsic: Start local sync timer on correct CPU
Date: Fri, 13 Jun 2025 19:03:02 +0200 [thread overview]
Message-ID: <87sek3poah.ffs@tglx> (raw)
In-Reply-To: <174957291849.2454024.7268696984666677694.git-patchwork-notify@kernel.org>
On Tue, Jun 10 2025 at 16:28, patchwork-bot wrote:
> Hello:
>
> This patch was applied to riscv/linux.git (fixes)
> by Thomas Gleixner <tglx@linutronix.de>:
No. I never apply patches to the riscv tree :)
> On Wed, 14 May 2025 10:13:20 -0700 you wrote:
>> When starting the local sync timer to synchronize the state of a remote
>> CPU it should be added on the CPU to be synchronized, not the initiating
>> CPU. This results in interrupt delivery being delayed until the timer
>> eventually runs (due to another mask/unmask/migrate operation) on the
>> target CPU.
>>
>> Fixes: 0f67911e821c ("irqchip/riscv-imsic: Separate next and previous pointers in IMSIC vector")
>> Signed-off-by: Andrew Bresticker <abrestic@rivosinc.com>
>>
>> [...]
>
> Here is the summary with links:
> - irqchip/riscv-imsic: Start local sync timer on correct CPU
> https://git.kernel.org/riscv/c/08fb624802d8
>
> You are awesome, thank you!
That patch has been committed to the tip tree and is already upstream.
Can you fix your bot scripts please?
prev parent reply other threads:[~2025-06-13 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 17:13 [PATCH] irqchip/riscv-imsic: Start local sync timer on correct CPU Andrew Bresticker
2025-05-15 6:39 ` Anup Patel
2025-05-15 15:27 ` [tip: irq/urgent] " tip-bot2 for Andrew Bresticker
2025-06-10 16:28 ` [PATCH] " patchwork-bot+linux-riscv
2025-06-13 17:03 ` Thomas Gleixner [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=87sek3poah.ffs@tglx \
--to=tglx@linutronix.de \
--cc=abrestic@rivosinc.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=patchwork-bot+linux-riscv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox