From: patchwork-bot+linux-riscv@kernel.org
To: Paul Walmsley <pjw@kernel.org>
Cc: linux-riscv@lists.infradead.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V updates for v6.19-rc7
Date: Mon, 26 Jan 2026 04:21:51 +0000 [thread overview]
Message-ID: <176940131135.4057692.4058115103852267681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <081aefd5-d47d-8397-693a-3e0a3c73783e@kernel.org>
Hello:
This pull request was applied to riscv/linux.git (fixes)
by Linus Torvalds <torvalds@linux-foundation.org>:
On Sat, 24 Jan 2026 16:21:29 -0700 (MST) you wrote:
> Linus,
>
> Please pull these RISC-V fixes for v6.19-rc7.
>
> The notable changes here are the three RISC-V timer compare register
> update sequence patches. These only apply to RV32 systems and are related
> to the 64-bit timer compare value being split across two separate 32-bit
> registers. We weren't using the appropriate three-write sequence,
> documented in the RISC-V ISA specifications, to avoid spurious timer
> interrupts during the update sequence; so, these patches now use the
> recommended sequence. This doesn't affect 64-bit RISC-V systems, since
> the timer compare value fits inside a single register and can be updated
> with a single write.
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V updates for v6.19-rc7
https://git.kernel.org/riscv/c/d91a46d6805a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-26 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 23:21 Paul Walmsley
2026-01-25 3:00 ` pr-tracker-bot
2026-01-26 4:21 ` patchwork-bot+linux-riscv [this message]
2026-01-26 4:24 ` patchwork-bot+linux-riscv
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=176940131135.4057692.4058115103852267681.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=pjw@kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome