Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Date:   Thu, 14 Sep 2023 11:16:59 +0100
From:   Joey Gouly <joey.gouly@arm.com>
To:     Mark Brown <broonie@kernel.org>
Cc:     Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will@kernel.org>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: Add some missing userspace ABI documentation
Message-ID: <20230914101659.GA1170646@e124191.cambridge.arm.com>
References: <20230914-arm64-feat-hbc-doc-v1-0-797d25f06897@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230914-arm64-feat-hbc-doc-v1-0-797d25f06897@kernel.org>
Precedence: bulk

On Thu, Sep 14, 2023 at 11:09:28AM +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.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Mark Brown (2):
>       arm64/hbc: Document HWCAP2_HBC
>       arm64: Document missing userspace visible fields in ID_AA64ISAR2_EL1
> 
>  Documentation/arch/arm64/cpu-feature-registers.rst | 10 ++++++++++
>  Documentation/arch/arm64/elf_hwcaps.rst            |  3 +++
>  2 files changed, 13 insertions(+)
> ---
> base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d
> change-id: 20230913-arm64-feat-hbc-doc-08e3d1741fdb
> 
> Best regards,
> -- 
> Mark Brown <broonie@kernel.org>
> 

I sent out a fix for this yesterday:
	https://lore.kernel.org/linux-arm-kernel/6162249d-dc0f-8755-9439-3ada8a88f424@arm.com/T/#t

Kristina also noticed cpu-feature-registers.rst hadn't been updated either, so I was just about to
send out a v2 that matches your patches. I won't do that since you've just done it!

Reviewed-by: Joey Gouly <joey.gouly@arm.com>

Thanks,
Joey