On Tue, Jan 14, 2014 at 02:26:27PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/cpufreq/speedstep-lib.c: In function 'speedstep_get_freqs': > drivers/cpufreq/speedstep-lib.c:467:2: error: implicit declaration of function 'preempt_check_resched' [-Werror=implicit-function-declaration] > preempt_check_resched(); > ^ > > Caused by commit 62b94a08da1b ("sched/preempt: Take away > preempt_enable_no_resched() from modules") interacting with commit > 24e1937b2386 ("speedstep-smi: enable interrupts when waiting") from the > pm tree. I think that pm commit is a very good example of why the sched/preempt patch is a very good idea. Also that Changelog fails to explain why enabling interrupts helps. What interrupt is required for progress, and how does it make the progress happen. -- 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