summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorLai Jiangshan <laijs@cn.fujitsu.com>2014-07-22 05:04:27 (GMT)
committerTejun Heo <tj@kernel.org>2014-07-22 16:10:39 (GMT)
commit29b1cb416a2920fbc70041e4382920ae2d86f426 (patch)
treed0571f5bc0132f5a600c066e858a308b105dc729 /net
parent13b1d625ef430ab7af059099828e1b9fba622369 (diff)
downloadlinux-29b1cb416a2920fbc70041e4382920ae2d86f426.tar.xz
workqueue: remove the stale comment in pwq_unbound_release_workfn()
In 75ccf5950f82 ("workqueue: prepare flush_workqueue() for dynamic creation and destrucion of unbound pool_workqueues"), a comment about the synchronization for the pwq in pwq_unbound_release_workfn() was added. The comment claimed the flush_mutex wasn't strictly necessary, it was correct in that time, due to the pwq was protected by workqueue_lock. But it is incorrect now since the wq->flush_mutex was renamed to wq->mutex and workqueue_lock was removed, the wq->mutex is strictly needed. But the comment was miss-updated when the synchronization was changed. This patch removes the incorrect comments and doesn't add any new comment to explain why wq->mutex is needed here, which is definitely obvious and wq->pwqs_node has "WQ" notation in its definition which is better comment. The old commit mentioned above also introduced a comment in link_pwq() about the synchronization. This comment is also removed in this patch since the whole link_pwq() is proteced by wq->mutex. Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions