[PATCHSET wq/for-3.12] workqueue: WQ_NON_REENTRANT is meaningless and going away

From: Tejun Heo
Date: Tue Jul 30 2013 - 08:43:44 EST


Hello,

dbf2576e37 ("workqueue: make all workqueues non-reentrant") made
WQ_NON_REENTRANT no-op but the following patches didn't remove the
flag or update the documentation. Let's mark the flag deprecated and
update the documentation accordingly and remove the existing usages.
We can remove the flag after the next merge window.

This patchset contains the following nine patches.

0001-workqueue-mark-WQ_NON_REENTRANT-deprecated.patch
0002-dm-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch
0003-mmc-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch
0004-firewire-WQ_NON_REENTRANT-is-meaningless-and-going-a.patch
0005-dlm-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch
0006-gfs2-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch
0007-xfs-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch
0008-ceph-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch
0009-l2tp-WQ_NON_REENTRANT-is-meaningless-and-going-away.patch

0001 marks the flag deprecated. The rest remove the exising usages.
This patchset as a whole doesn't introduce any behavior changes.

0001 is already applied to wq/for-3.12. The rest will be routed
through the respective trees. The patches are also available in the
following git branch.

git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git review-WQ_NON_REENTRANT-removal

Documentation/workqueue.txt | 18 ++++++------------
drivers/firewire/core-transaction.c | 3 +--
drivers/md/dm-crypt.c | 10 ++--------
drivers/md/dm-kcopyd.c | 3 +--
drivers/md/dm-raid1.c | 3 +--
drivers/md/dm.c | 3 +--
drivers/mmc/host/dw_mmc.c | 2 +-
fs/dlm/ast.c | 5 +----
fs/gfs2/main.c | 2 +-
fs/xfs/xfs_super.c | 6 +++---
include/linux/workqueue.h | 7 ++++++-
net/ceph/messenger.c | 2 +-
net/l2tp/l2tp_core.c | 2 +-
13 files changed, 26 insertions(+), 40 deletions(-)

Thanks.

--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/