[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170298019769.1509727.6589504598690487361.b4-ty@kernel.org>
Date: Tue, 19 Dec 2023 11:18:30 +0000
From: Will Deacon <will@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>,
Mark Brown <broonie@...nel.org>,
Shuah Khan <shuah@...nel.org>
Cc: kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Don't probe the current VL for unsupported vector types
On Mon, 18 Dec 2023 23:39:32 +0000, Mark Brown wrote:
> The vec-syscfg selftest verifies that setting the VL of the currently
> tested vector type does not disrupt the VL of the other vector type. To do
> this it records the current vector length for each type but neglects to
> guard this with a check for that vector type actually being supported. Add
> one, using a helper function which we also update all the other instances
> of this pattern.
>
> [...]
Applied to arm64 (for-next/selftests), thanks!
[1/1] kselftest/arm64: Don't probe the current VL for unsupported vector types
https://git.kernel.org/arm64/c/9a802ddb2123
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists