From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] kselftest/arm64: Minor SME signals test additions
Date: Fri, 20 Jan 2023 16:58:59 +0000 [thread overview]
Message-ID: <167423393397.2326323.2802825304933346792.b4-ty@arm.com> (raw)
In-Reply-To: <20230117-arm64-test-ssve-za-v1-0-203c00150154@kernel.org>
On Fri, 20 Jan 2023 12:04:08 +0000, Mark Brown wrote:
> While discussing the SME signal handling support I realised that
> we were not verifying that SVE_SIG_FLAG_SM is set for streaming
> SVE, and not explicitly covering the case where we are both in
> streaming mode and have ZA enabled. Add coverage of these cases,
> I didn't find any problems running these new tests.
>
>
> [...]
Applied to arm64 (for-next/kselftest), thanks!
[1/2] kselftest/arm64: Verify that SSVE signal context has SVE_SIG_FLAG_SM set
https://git.kernel.org/arm64/c/f76cb73a2d7c
[2/2] kselftest/arm64: Verify simultaneous SSVE and ZA context generation
https://git.kernel.org/arm64/c/bc69da5ff087
--
Catalin
prev parent reply other threads:[~2023-01-20 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 12:04 [PATCH 0/2] kselftest/arm64: Minor SME signals test additions Mark Brown
2023-01-20 12:04 ` [PATCH 1/2] kselftest/arm64: Verify that SSVE signal context has SVE_SIG_FLAG_SM set Mark Brown
2023-01-20 12:04 ` [PATCH 2/2] kselftest/arm64: Verify simultaneous SSVE and ZA context generation Mark Brown
2023-01-20 16:58 ` Catalin Marinas [this message]
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=167423393397.2326323.2802825304933346792.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).