[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174369723749.2563936.8850444880196164283.git-patchwork-notify@kernel.org>
Date: Thu, 03 Apr 2025 16:20:37 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Ignacio Encinas <ignacio@...cinas.com>
Cc: linux-riscv@...ts.infradead.org, linux-kernel-mentees@...ts.linux.dev,
skhan@...uxfoundation.org, paul.walmsley@...ive.com, palmer@...belt.com,
alex@...ti.fr, charlie@...osinc.com, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] selftests: riscv: fix v_exec_initval_nolibc.c
Hello:
This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@...osinc.com>:
On Thu, 06 Mar 2025 20:49:27 +0100 you wrote:
> Vector registers are zero initialized by the kernel. Stop accepting
> "all ones" as a clean value.
>
> Note that this was not working as expected given that
> value == 0xff
> can be assumed to be always false by the compiler as value's range is
> [-128, 127]. Both GCC (-Wtype-limits) and clang
> (-Wtautological-constant-out-of-range-compare) warn about this.
>
> [...]
Here is the summary with links:
- [v2] selftests: riscv: fix v_exec_initval_nolibc.c
https://git.kernel.org/riscv/c/79ba5c1c7767
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists