[PATCH v1 2/2] kselftest/arm64: Correct logging of FPSIMD register read via ptrace
Shuah Khan
skhan at linuxfoundation.org
Mon Jan 24 13:28:29 PST 2022
On 1/24/22 10:55 AM, Mark Brown wrote:
> There's a cut'n'paste error in the logging for our test for reading register
> state back via ptrace, correctly say that we did a read instead of a write.
>
> Signed-off-by: Mark Brown <broonie at kernel.org>
> ---
> tools/testing/selftests/arm64/fp/sve-ptrace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/arm64/fp/sve-ptrace.c b/tools/testing/selftests/arm64/fp/sve-ptrace.c
> index 0cf78360c5bc..a3c1e67441f9 100644
> --- a/tools/testing/selftests/arm64/fp/sve-ptrace.c
> +++ b/tools/testing/selftests/arm64/fp/sve-ptrace.c
> @@ -261,7 +261,7 @@ static void ptrace_sve_fpsimd(pid_t child, const struct vec_type *type)
> }
>
> ksft_test_result((sve->flags & SVE_PT_REGS_MASK) == SVE_PT_REGS_FPSIMD,
> - "Set FPSIMD registers via %s\n", type->name);
> + "Got FPSIMD registers via %s\n", type->name);
> if ((sve->flags & SVE_PT_REGS_MASK) != SVE_PT_REGS_FPSIMD)
> goto out;
>
>
Looks good to me. Assuming this is going through ARM tree
Reviewed-by: Shuah Khan <skhan at linuxfoundation.org>
thanks,
-- Shuah
More information about the linux-arm-kernel
mailing list