From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 3/3] arm64/hwcap: Support FEAT_EBF16
Date: Thu, 7 Jul 2022 12:40:16 +0100 [thread overview]
Message-ID: <YsbGIHji1rCgVCZD@arm.com> (raw)
In-Reply-To: <20220707103632.12745-4-broonie@kernel.org>
On Thu, Jul 07, 2022 at 11:36:32AM +0100, Mark Brown wrote:
> diff --git a/arch/arm64/include/uapi/asm/hwcap.h b/arch/arm64/include/uapi/asm/hwcap.h
> index fd7577cf8e77..1ad2568a2569 100644
> --- a/arch/arm64/include/uapi/asm/hwcap.h
> +++ b/arch/arm64/include/uapi/asm/hwcap.h
> @@ -91,5 +91,6 @@
> #define HWCAP2_SME_F32F32 (1 << 29)
> #define HWCAP2_SME_FA64 (1 << 30)
> #define HWCAP2_WFXT (1UL << 31)
> +#define HWCAP2_EBF16 (1UL << 32)
This works for me:
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-07-07 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 10:36 [PATCH v5 0/3] arm64: Start allocating upper bits of AT_HWCAP2 Mark Brown
2022-07-07 10:36 ` [PATCH v5 1/3] arm64/hwcap: Document allocation of upper bits of AT_HWCAP Mark Brown
2022-07-07 11:21 ` Szabolcs Nagy
2022-07-07 11:38 ` Catalin Marinas
2022-07-07 10:36 ` [PATCH v5 2/3] arm64/cpufeature: Store elf_hwcaps as a bitmap rather than unsigned long Mark Brown
2022-07-07 11:37 ` Catalin Marinas
2022-07-07 11:52 ` Mark Brown
2022-07-07 10:36 ` [PATCH v5 3/3] arm64/hwcap: Support FEAT_EBF16 Mark Brown
2022-07-07 11:40 ` Catalin Marinas [this message]
2022-07-20 12:29 ` [PATCH v5 0/3] arm64: Start allocating upper bits of AT_HWCAP2 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=YsbGIHji1rCgVCZD@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=szabolcs.nagy@arm.com \
--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.