[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120702123740.GA11168@sirena.org.uk>
Date: Mon, 2 Jul 2012 13:37:40 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: ShuoX Liu <shuox.liu@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Build failures in -next due to move of disable
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:
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists