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

[Dave Jones]

On Wed, Apr 27, 2011 at 11:54:27AM +1000, Stephen Rothwell wrote:
 > Hi Dave,
 > 
 > On Tue, 26 Apr 2011 21:32:17 -0400 Dave Jones <davej@xxxxxxxxxx> 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:

I've moved this work onto a separate move-drivers branch. Could you track that in next too please?
(Apply after fixes & next)

I'm hoping this branch will be fairly short-lived, but it depends how quickly
other architecture maintainers move their drivers over too.

thanks,

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/