From: patchwork-bot+linux-riscv@kernel.org
To: Andreas Schwab <schwab@suse.de>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv/futex: sign extend compare value in atomic cmpxchg
Date: Thu, 13 Feb 2025 18:30:41 +0000 [thread overview]
Message-ID: <173947144178.1330575.8179936961826705707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <mvmfrkv2vhz.fsf@suse.de>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 03 Feb 2025 11:06:00 +0100 you wrote:
> Make sure the compare value in the lr/sc loop is sign extended to match
> what lr.w does. Fortunately, due to the compiler keeping the register
> contents sign extended anyway the lack of the explicit extension didn't
> result in wrong code so far, but this cannot be relied upon.
>
> Fixes: b90edb33010b ("RISC-V: Add futex support.")
> Signed-off-by: Andreas Schwab <schwab@suse.de>
>
> [...]
Here is the summary with links:
- riscv/futex: sign extend compare value in atomic cmpxchg
https://git.kernel.org/riscv/c/5c238584bce5
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:[~2025-02-13 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 10:06 [PATCH] riscv/futex: sign extend compare value in atomic cmpxchg Andreas Schwab
2025-02-03 15:33 ` Björn Töpel
2025-02-03 15:44 ` Andreas Schwab
2025-02-03 21:25 ` Jessica Clarke
2025-02-04 8:28 ` Andreas Schwab
2025-02-04 8:44 ` Alexandre Ghiti
2025-02-13 18:30 ` patchwork-bot+linux-riscv [this message]
2025-02-14 4:11 ` [External] " yunhui cui
2025-02-14 6:04 ` [External] " Jessica Clarke
2025-02-14 6:22 ` yunhui cui
2025-02-14 7:17 ` Jessica Clarke
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=173947144178.1330575.8179936961826705707.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=schwab@suse.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