From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ShuoX Liu <shuox.liu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Build failures in -next due to move of disable
Date: Mon, 2 Jul 2012 21:54:35 +0200 [thread overview]
Message-ID: <201207022154.35327.rjw@sisk.pl> (raw)
In-Reply-To: <20120702123740.GA11168@sirena.org.uk>
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'
>
>
next prev parent reply other threads:[~2012-07-02 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 12:37 Mark Brown
2012-07-02 19:54 ` Rafael J. Wysocki [this message]
2012-07-02 19:53 ` Andrew Morton
2012-07-02 20:16 ` Rafael J. Wysocki
2012-07-02 21:37 ` Rafael J. Wysocki
2012-07-03 17:13 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201207022154.35327.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuox.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®