From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: linux-next: build failure after merge of the cpufreq tree
Date: Wed, 29 Feb 2012 22:01:25 -0500 [thread overview]
Message-ID: <20120301030125.GA27070@redhat.com> (raw)
In-Reply-To: <20120301135601.a164a12e2bd4aee871ff60db@canb.auug.org.au>
On Thu, Mar 01, 2012 at 01:56:01PM +1100, Stephen Rothwell wrote:
> Hi Dave,
>
> After merging the cpufreq tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/cpufreq/cpufreq_ondemand.c: In function 'cpufreq_gov_dbs_init':
> drivers/cpufreq/cpufreq_ondemand.c:880:28: error: 'PM_QOS_DVFS_RESPONSE_LATENCY' undeclared (first use in this function)
> drivers/cpufreq/cpufreq_ondemand.c: In function 'cpufreq_gov_dbs_exit':
> drivers/cpufreq/cpufreq_ondemand.c:896:25: error: 'PM_QOS_DVFS_RESPONSE_LATENCY' undeclared (first use in this function)
>
> Caused by commit 500e8ca39c56 ("[CPUFREQ] ondemand: handle QoS request on
> DVFS response latency").
>
> I have used the cpufreq tree fomr next-20120229 for today.
gah, this patch was dependant upon another that didn't apply cleanly.
Dave
next prev parent reply other threads:[~2012-03-01 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 2:56 linux-next: build failure after merge of the cpufreq tree Stephen Rothwell
2012-03-01 3:01 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-05 1:46 MyungJoo Ham
2012-03-05 1:46 ` MyungJoo Ham
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=20120301030125.GA27070@redhat.com \
--to=davej@redhat.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.