From: Dev Jain <dev.jain@arm.com>
To: Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] kselftest/arm64: Fix check for setting new VLs in sve-ptrace
Date: Mon, 26 May 2025 16:23:25 +0530 [thread overview]
Message-ID: <ba4a5dce-2440-4e31-8fa3-0c104c091797@arm.com> (raw)
In-Reply-To: <20250523-kselftest-arm64-ssve-fixups-v1-1-65069a263b21@kernel.org>
On 23/05/25 8:57 pm, Mark Brown wrote:
> The check that the new vector length we set was the expected one was typoed
> to an assignment statement which for some reason the compilers didn't spot,
> most likely due to the macros involved.
>
> Fixes: 0dca276ac4d2 ("selftests: arm64: Add test for the SVE ptrace interface")
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Dev Jain <dev.jain@arm.com>
>
next prev parent reply other threads:[~2025-05-26 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 15:27 [PATCH 0/3] kselftest/arm64: Update sve-ptrace for ABI changes Mark Brown
2025-05-23 15:27 ` [PATCH 1/3] kselftest/arm64: Fix check for setting new VLs in sve-ptrace Mark Brown
2025-05-26 10:30 ` Mark Rutland
2025-05-26 10:53 ` Dev Jain [this message]
2025-05-23 15:27 ` [PATCH 2/3] kselftest/arm64: Fix test for streaming FPSIMD write " Mark Brown
2025-05-26 10:44 ` Mark Rutland
2025-05-23 15:27 ` [PATCH 3/3] kselftest/arm64: Specify SVE data when testing VL set " Mark Brown
2025-05-26 10:57 ` Mark Rutland
2025-05-26 10:23 ` [PATCH 0/3] kselftest/arm64: Update sve-ptrace for ABI changes Mark Rutland
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=ba4a5dce-2440-4e31-8fa3-0c104c091797@arm.com \
--to=dev.jain@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=will@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