From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v1 2/6] kselftest/arm64: Add FEAT_CSSC to the hwcap selftest
Date: Wed, 9 Nov 2022 17:30:32 +0000 [thread overview]
Message-ID: <Y2vjuNa+jXseQyvA@arm.com> (raw)
In-Reply-To: <20221017152520.1039165-3-broonie@kernel.org>
On Mon, Oct 17, 2022 at 04:25:16PM +0100, Mark Brown wrote:
> Add FEAT_CSSC to the set of features checked by the hwcap selftest.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v1 2/6] kselftest/arm64: Add FEAT_CSSC to the hwcap selftest
Date: Wed, 9 Nov 2022 17:30:32 +0000 [thread overview]
Message-ID: <Y2vjuNa+jXseQyvA@arm.com> (raw)
In-Reply-To: <20221017152520.1039165-3-broonie@kernel.org>
On Mon, Oct 17, 2022 at 04:25:16PM +0100, Mark Brown wrote:
> Add FEAT_CSSC to the set of features checked by the hwcap selftest.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-09 17:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 15:25 [PATCH v1 0/6] arm64: Support for 2022 data processing instructions Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-10-17 15:25 ` [PATCH v1 1/6] arm64/hwcap: Add support for FEAT_CSSC Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-11-09 17:29 ` Catalin Marinas
2022-11-09 17:29 ` Catalin Marinas
2022-10-17 15:25 ` [PATCH v1 2/6] kselftest/arm64: Add FEAT_CSSC to the hwcap selftest Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-11-09 17:30 ` Catalin Marinas [this message]
2022-11-09 17:30 ` Catalin Marinas
2022-10-17 15:25 ` [PATCH v1 3/6] arm64/hwcap: Add support for FEAT_RPRFM Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-11-09 17:30 ` Catalin Marinas
2022-11-09 17:30 ` Catalin Marinas
2022-10-17 15:25 ` [PATCH v1 4/6] kselftest/arm64: Add FEAT_RPRFM to the hwcap test Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-11-09 17:31 ` Catalin Marinas
2022-11-09 17:31 ` Catalin Marinas
2022-10-17 15:25 ` [PATCH v1 5/6] arm64/hwcap: Add support for SVE 2.1 Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-11-09 17:35 ` Catalin Marinas
2022-11-09 17:35 ` Catalin Marinas
2022-10-17 15:25 ` [PATCH v1 6/6] kselftest/arm64: Add SVE 2.1 to hwcap test Mark Brown
2022-10-17 15:25 ` Mark Brown
2022-11-09 17:35 ` Catalin Marinas
2022-11-09 17:35 ` Catalin Marinas
2022-11-09 19:13 ` [PATCH v1 0/6] arm64: Support for 2022 data processing instructions Will Deacon
2022-11-09 19:13 ` Will Deacon
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=Y2vjuNa+jXseQyvA@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.