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:	Mon, 2 Jul 2012 21:54:35 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	ShuoX Liu <shuox.liu@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Build failures in -next due to move of disable

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@...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

Powered by Openwall GNU/*/Linux Powered by OpenVZ