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 1/3] arm64/hwcap: Document allocation of upper bits of AT_HWCAP
Date: Thu, 7 Jul 2022 12:38:21 +0100 [thread overview]
Message-ID: <YsbFrUtP4UFbihmS@arm.com> (raw)
In-Reply-To: <20220707103632.12745-2-broonie@kernel.org>
On Thu, Jul 07, 2022 at 11:36:30AM +0100, Mark Brown wrote:
> The top two bits of AT_HWCAP are reserved for use by glibc and the rest of
> the top 32 bits are being kept unallocated for potential use by glibc.
> Document this in the header.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-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:39 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 [this message]
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
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=YsbFrUtP4UFbihmS@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 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).