Re: Build failures in -next due to move of disable

[Rafael J. Wysocki]

On Monday, July 02, 2012, Mark Brown wrote:
> Today's -next is failing to build for me because commit 9f419c (PM /
> Domains: Add preliminary support for cpuidle) and commit b32e30
> (cpuidle: move field disable from per-driver to per-cpu) disagree about
> where the disable field should be:

Hmm, do you know what tree commit b32e30 comes from?

Rafael


> 
>   CC      drivers/base/power/domain.o
> drivers/base/power/domain.c: In function '__pm_genpd_poweron':
> drivers/base/power/domain.c:194: error: 'struct cpuidle_state' has no member named 'disable'
> drivers/base/power/domain.c: In function 'pm_genpd_poweroff':
> drivers/base/power/domain.c:490: error: 'struct cpuidle_state' has no member named 'disable'
> drivers/base/power/domain.c: In function 'genpd_attach_cpuidle':
> drivers/base/power/domain.c:1671: error: 'struct cpuidle_state' has no member named 'disable'
> drivers/base/power/domain.c: In function 'genpd_detach_cpuidle':
> drivers/base/power/domain.c:1706: error: 'struct cpuidle_state' has no member named 'disable'
> 
> 

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