From: Catalin Marinas <catalin.marinas@arm.com>
To: will@kernel.org, shuah@kernel.org, broonie@kernel.org,
yeoreum.yun@arm.com, jonathan.cameron@huawei.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linuxarm@huawei.com,
Yifan Wu <wuyifan50@huawei.com>
Cc: xiaqinxin@huawei.com, prime.zeng@hisilicon.com,
wangyushan12@huawei.com, xuwei5@huawei.com, fanghao11@huawei.com,
wangzhou1@hisilicon.com
Subject: Re: (subset) [PATCH v2 0/2] selftests/arm64: Fix sve2p1_sigill() and add cmpbr_sigill() for hwcap test
Date: Fri, 27 Mar 2026 13:00:35 +0000 [thread overview]
Message-ID: <acZ_cxnUjoFiAuJp@arm.com> (raw)
In-Reply-To: <177461612664.2271410.12022212735709481989.b4-ty@arm.com>
On Fri, Mar 27, 2026 at 12:58:11PM +0000, Catalin Marinas wrote:
> On Thu, 05 Mar 2026 09:36:36 +0800, Yifan Wu wrote:
> > This patch series fixes and adds two selftests in the arm64 hwcap
> > test suite.
> >
> > Patch 1/2 fixes the sve2p1_sigill() test to correctly detect the
> > FEAT_SVE2p1 feature. Previously, the test incorrectly assumed that
> > the presence of FEAT_SVE2.1 implied support for the BFADD
> > instruction, which actually depends on the FEAT_SVE_B16B16 feature.
> > The test is updated to use the LD1Q instruction, which is
> > unambiguously implied by FEAT_SVE2p1.
> >
> > [...]
>
> Applied to arm64 (for-kernelci), thanks!
Wrong branch, it's for-next/kselftest (script got confused).
prev parent reply other threads:[~2026-03-27 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 1:36 [PATCH v2 0/2] selftests/arm64: Fix sve2p1_sigill() and add cmpbr_sigill() for hwcap test Yifan Wu
2026-03-05 1:36 ` [PATCH v2 1/2] selftest/arm64: Fix sve2p1_sigill() to " Yifan Wu
2026-03-05 1:36 ` [PATCH v2 2/2] selftests/arm64: Implement cmpbr_sigill() " Yifan Wu
2026-03-05 14:15 ` Mark Brown
2026-03-06 12:26 ` [PATCH v2 0/2] selftests/arm64: Fix sve2p1_sigill() and add cmpbr_sigill() for " Will Deacon
2026-03-27 5:59 ` wuyifan
2026-03-27 12:58 ` (subset) " Catalin Marinas
2026-03-27 13:00 ` 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=acZ_cxnUjoFiAuJp@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=fanghao11@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=shuah@kernel.org \
--cc=wangyushan12@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=wuyifan50@huawei.com \
--cc=xiaqinxin@huawei.com \
--cc=xuwei5@huawei.com \
--cc=yeoreum.yun@arm.com \
/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