linux-kernel - Re: [PATCH 043/104] drivers/cpufreq: remove depends on CONFIG

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <5936896.ObBXSaEhRc@vostro.rjw.lan>
Date:	Tue, 06 Nov 2012 14:49:16 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Kees Cook <keescook@...omium.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 043/104] drivers/cpufreq: remove depends on CONFIG_EXPERIMENTAL

On Monday, November 05, 2012 03:04:00 PM Kees Cook wrote:
> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
> while now and is almost always enabled by default. As agreed during the
> Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
> 
> CC: "Rafael J. Wysocki" <rjw@...k.pl>
> Signed-off-by: Kees Cook <keescook@...omium.org>

Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

> ---
>  drivers/cpufreq/Kconfig.arm |    4 ++--
>  drivers/cpufreq/Kconfig.x86 |    6 +++---
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index 5961e64..b63c335 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -21,8 +21,8 @@ config ARM_S3C2416_CPUFREQ
>  	  If in doubt, say N.
>  
>  config ARM_S3C2416_CPUFREQ_VCORESCALE
> -	bool "Allow voltage scaling for S3C2416 arm core (EXPERIMENTAL)"
> -	depends on ARM_S3C2416_CPUFREQ && REGULATOR && EXPERIMENTAL
> +	bool "Allow voltage scaling for S3C2416 arm core"
> +	depends on ARM_S3C2416_CPUFREQ && REGULATOR
>  	help
>  	  Enable CPU voltage scaling when entering the dvs mode.
>  	  It uses information gathered through existing hardware and
> diff --git a/drivers/cpufreq/Kconfig.x86 b/drivers/cpufreq/Kconfig.x86
> index 934854a..0715d8e 100644
> --- a/drivers/cpufreq/Kconfig.x86
> +++ b/drivers/cpufreq/Kconfig.x86
> @@ -174,7 +174,7 @@ config X86_SPEEDSTEP_ICH
>  config X86_SPEEDSTEP_SMI
>  	tristate "Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface)"
>  	select CPU_FREQ_TABLE
> -	depends on X86_32 && EXPERIMENTAL
> +	depends on X86_32
>  	help
>  	  This adds the CPUFreq driver for certain mobile Intel Pentium III
>  	  (Coppermine), all mobile Intel Pentium III-M (Tualatin)
> @@ -206,7 +206,7 @@ config X86_P4_CLOCKMOD
>  
>  config X86_CPUFREQ_NFORCE2
>  	tristate "nVidia nForce2 FSB changing"
> -	depends on X86_32 && EXPERIMENTAL
> +	depends on X86_32
>  	help
>  	  This adds the CPUFreq driver for FSB changing on nVidia nForce2
>  	  platforms.
> @@ -242,7 +242,7 @@ config X86_LONGHAUL
>  config X86_E_POWERSAVER
>  	tristate "VIA C7 Enhanced PowerSaver (DANGEROUS)"
>  	select CPU_FREQ_TABLE
> -	depends on X86_32 && EXPERIMENTAL
> +	depends on X86_32
>  	help
>  	  This adds the CPUFreq driver for VIA C7 processors.  However, this driver
>  	  does not have any safeguards to prevent operating the CPU out of spec
> 
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/