linux-kernel - Re: chrome platform Kconfig typo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b992473c-45ff-6cd5-3b09-0c1947d76e1d@collabora.com>
Date:   Thu, 5 Mar 2020 10:00:21 +0100
From:   Enric Balletbo i Serra <enric.balletbo@...labora.com>
To:     Randy Dunlap <rdunlap@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Benson Leung <bleung@...omium.org>
Subject: Re: chrome platform Kconfig typo

Hi Randy,

On 5/3/20 8:11, Randy Dunlap wrote:
> 
> from drivers/platform/chrome/Kconfig:
> 
> config MFD_CROS_EC
> 	tristate "Platform support for Chrome hardware (transitional)"
> 	select CHROME_PLATFORMS
> 	select CROS_EC
> 	select CONFIG_MFD_CROS_EC_DEV   <<<<<<<<<<<<<<<<<<<<<<   drop the /CONFIG_/ <<<<<<<<<<<<<<

Thanks for the report I'll send a patch. Our plan was remove this config at some
point and that makes me think if this transitional config was ever useful, seems
there is still a defconfig using it, though, so we can't remove yet.

> 	depends on X86 || ARM || ARM64 || COMPILE_TEST
> 	help
> 	  This is a transitional Kconfig option and will be removed after
> 	  everyone enables the parts individually.
> 
>