Received-SPF: pass (google.com: domain of linux-kernel+bounces-5065-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Mark Brown <broonie@kernel.org>,
	Shuah Khan <shuah@kernel.org>
Cc: kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Don't probe the current VL for unsupported vector types
Date: Tue, 19 Dec 2023 11:18:30 +0000
Message-Id: <170298019769.1509727.6589504598690487361.b4-ty@kernel.org>
In-Reply-To: <20231218-kselftest-arm64-vec-syscfg-rdvl-v1-1-0ac22d47e81f@kernel.org>
References: <20231218-kselftest-arm64-vec-syscfg-rdvl-v1-1-0ac22d47e81f@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

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