[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07190b99-5e8c-4de0-b460-248ec39996f4@sirena.org.uk>
Date: Wed, 11 Jun 2025 14:34:35 +0100
From: Mark Brown <broonie@...nel.org>
To: Yeoreum Yun <yeoreum.yun@....com>
Cc: catalin.marinas@....com, will@...nel.org, maz@...nel.org,
oliver.upton@...ux.dev, ardb@...nel.org, frederic@...nel.org,
james.morse@....com, joey.gouly@....com,
scott@...amperecomputing.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/6] arm64/Kconfig: add LSUI Kconfig
On Wed, Jun 11, 2025 at 11:49:12AM +0100, Yeoreum Yun wrote:
> +menu "v9.6 architectural features"
> +
> +config AS_HAS_LSUI
> + def_bool $(as-instr,.arch_extension lsui)
> +
> +endmenu # "v9.6 architectural features"
> +
This is adding a menu with no user selectable options, does that not
result in a confusing user experience? We do often add toolchain
feature checks inside the menus but that's usually associated with
hiding a user selectable option, if there isn't one (or any other option
for that arch version yet) we should probably put the check elsewhere.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists