freezer: don't unnecessarily set PF_NOFREEZE explicitly
authorTejun Heo <tj@kernel.org>
Mon, 21 Nov 2011 20:32:22 +0000 (12:32 -0800)
committerTejun Heo <tj@kernel.org>
Mon, 21 Nov 2011 20:32:22 +0000 (12:32 -0800)
commit3a7cbd50f74907580eb47a8d08e1f29741b81abf
tree515b7d9b9fa85c20ecf6779d563371b666a8b991
parent50fb4f7fc907efff65eadb0b74387a9ffed6e849
freezer: don't unnecessarily set PF_NOFREEZE explicitly

Some drivers set PF_NOFREEZE in their kthread functions which is
completely unnecessary and racy - some part of freezer code doesn't
consider cases where PF_NOFREEZE is set asynchronous to freezer
operations.

In general, there's no reason to allow setting PF_NOFREEZE explicitly.
Remove them and change the documentation to note that setting
PF_NOFREEZE directly isn't allowed.

-v2: Dropped change to twl4030-irq.c as it no longer uses PF_NOFREEZE.

Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: "Gustavo F. Padovan" <padovan@profusion.mobi>
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Cc: Marcel Holtmann <marcel@holtmann.org>
Cc: wwang <wei_wang@realsil.com.cn>
Documentation/power/freezing-of-tasks.txt
drivers/bluetooth/btmrvl_main.c
drivers/mfd/twl6030-irq.c
drivers/staging/rts_pstor/rtsx.c