linux-kernel - Re: linux-next: build warning after merge of the cpufreq tree

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]

Date:	Wed, 27 Apr 2011 11:54:27 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Dave Jones <davej@...hat.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the cpufreq tree

Hi Dave,

On Tue, 26 Apr 2011 21:32:17 -0400 Dave Jones <davej@...hat.com> wrote:
>
> As the commit message suggests, per-arch cpufreq drivers are moving to drivers/cpufreq/
> So far, I've only moved the x86 ones.  As a side-effect of this, the 
> source "drivers/cpufreq/Kconfig" is no longer a per-arch thing, as it now gets
> included from kernel/power/Kconfig.
> 
> I suspect the warnings are happening because on the unconverted archs, drivers/cpufreq/Kconfig
> is now getting included twice.  If you kill the 'source' line in kernel/power/Kconfig,
> does this make things go back to normal ?  (Check that cpufreq still shows up in
> the resulting config afterwards)

Removing the source line in kernel/power/Kconfig makes the warnings go
away and the only change in the generated config file is this:

@@ -465,10 +465,6 @@
 # CONFIG_PM_RUNTIME is not set
 CONFIG_PM=y
 # CONFIG_PM_DEBUG is not set
-
-#
-# CPU Frequency scaling
-#
 CONFIG_SECCOMP=y
 CONFIG_ISA_DMA_API=y

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped