[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120301030125.GA27070@redhat.com>
Date: Wed, 29 Feb 2012 22:01:25 -0500
From: Dave Jones <davej@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: linux-next: build failure after merge of the cpufreq tree
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
--
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