From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: Add some missing userspace ABI documentation
Date: Mon, 18 Sep 2023 12:05:15 +0100 [thread overview]
Message-ID: <169503047379.1328612.6715103972434171186.b4-ty@kernel.org> (raw)
In-Reply-To: <20230914-arm64-feat-hbc-doc-v1-0-797d25f06897@kernel.org>
On Thu, 14 Sep 2023 11:09:28 +0100, Mark Brown wrote:
> I noticed that we've added HWCAP2_HBC without updating the
> documentation, and in the process also noticed that some user visible
> fields in ID_AA64ISAR2_EL1 are not documented. Fix these issues.
>
> Given the lack of any automatic generation or auditing there's almost
> certainly more fields that are broken in cpu-feature-registers.rst, I
> didn't check any other registers.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/2] arm64/hbc: Document HWCAP2_HBC
https://git.kernel.org/arm64/c/5ad361f42fe4
[2/2] arm64: Document missing userspace visible fields in ID_AA64ISAR2_EL1
https://git.kernel.org/arm64/c/44a5b6b5c7fe
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-09-18 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 10:09 Mark Brown
2023-09-14 10:09 ` [PATCH 1/2] arm64/hbc: Document HWCAP2_HBC Mark Brown
2023-09-14 10:09 ` [PATCH 2/2] arm64: Document missing userspace visible fields in ID_AA64ISAR2_EL1 Mark Brown
2023-09-14 10:16 ` [PATCH 0/2] arm64: Add some missing userspace ABI documentation Joey Gouly
2023-09-18 11:05 ` Will Deacon [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=169503047379.1328612.6715103972434171186.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®