Re: linux-next: build failure after merge of the cpufreq tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux