diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-09-19 18:00:07 (GMT) |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-09-19 18:00:07 (GMT) |
commit | c5c473e29c641380aef4a9d1f9c39de49219980f (patch) | |
tree | 7cc1d52fa7757ecd0903fc6e86bb22188d2a8bbd /drivers/gpio/gpio-pca953x.c | |
parent | 925a6f0bf8bd122d5d2429af7f0ca0fecf4ae71f (diff) | |
parent | 6889125b8b4e09c5e53e6ecab3433bed1ce198c9 (diff) | |
download | linux-fsl-qoriq-c5c473e29c641380aef4a9d1f9c39de49219980f.tar.xz |
Merge branch 'for-3.6-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
Pull workqueue / powernow-k8 fix from Tejun Heo:
"This is the fix for the bug where cpufreq/powernow-k8 was tripping
BUG_ON() in try_to_wake_up_local() by migrating workqueue worker to a
different CPU.
https://bugzilla.kernel.org/show_bug.cgi?id=47301
As discussed, the fix is now two parts - one to reimplement
work_on_cpu() so that it doesn't create a new kthread each time and
the actual fix which makes powernow-k8 use work_on_cpu() instead of
performing manual migration.
While pretty late in the merge cycle, both changes are on the safer
side. Jiri and I verified two existing users of work_on_cpu() and
Duncan confirmed that the powernow-k8 fix survived about 18 hours of
testing."
* 'for-3.6-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq:
cpufreq/powernow-k8: workqueue user shouldn't migrate the kworker to another CPU
workqueue: reimplement work_on_cpu() using system_wq
Diffstat (limited to 'drivers/gpio/gpio-pca953x.c')
0 files changed, 0 insertions, 0 deletions