linux-kernel - Re: [PATCH] powercap/rapl: fix build dependency on iosf

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]

Date:	Thu, 13 Nov 2014 02:34:06 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Rafael Wysocki <rafael.j.wysocki@...el.com>,
	Linux PM <linux-pm@...r.kernel.org>,
	Ajay Thomas <ajay.thomas.david.rajamanickam@...el.com>
Subject: Re: [PATCH] powercap/rapl: fix build dependency on iosf_mbi

On Wednesday, November 12, 2014 10:50:36 AM Jacob Pan wrote:
> RAPL on Atom depends on IOSF_MBI driver for setting
> floor frequency. This patch adds explicit dependency on
> CONFIG_IOSF_MB.
> 
> Signed-off-by: Jacob Pan <jacob.jun.pan@...ux.intel.com>

Applied, thanks!

> ---
>  drivers/powercap/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/powercap/Kconfig b/drivers/powercap/Kconfig
> index a7c81b5..85727ef 100644
> --- a/drivers/powercap/Kconfig
> +++ b/drivers/powercap/Kconfig
> @@ -17,7 +17,7 @@ if POWERCAP
>  # Client driver configurations go here.
>  config INTEL_RAPL
>  	tristate "Intel RAPL Support"
> -	depends on X86
> +	depends on X86 && IOSF_MBI
>  	default n
>  	---help---
>  	  This enables support for the Intel Running Average Power Limit (RAPL)
> 

-- 
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/