public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com
Cc: shli@kernel.org
Subject: [PATCHSET wq/for-3.12] workqueue: WQ_NON_REENTRANT is meaningless and going away
Date: Tue, 30 Jul 2013 08:40:19 -0400	[thread overview]
Message-ID: <1375188028-11910-1-git-send-email-tj@kernel.org> (raw)

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

             reply	other threads:[~2013-07-30 12:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 12:40 Tejun Heo [this message]
2013-07-30 12:40 ` [PATCH 1/9] workqueue: mark WQ_NON_REENTRANT deprecated Tejun Heo
2013-07-31  6:12   ` Lai Jiangshan
2013-07-30 12:40 ` [PATCH 2/9] dm: WQ_NON_REENTRANT is meaningless and going away Tejun Heo
2013-07-30 12:40 ` [PATCH 3/9] mmc: " Tejun Heo
2013-07-30 12:40 ` [PATCH 4/9] firewire: " Tejun Heo
2013-07-30 13:52   ` Stefan Richter
2013-07-30 12:40 ` [PATCH 5/9] dlm: " Tejun Heo
2013-07-30 12:40 ` [PATCH 6/9] gfs2: " Tejun Heo
2013-07-30 14:10   ` Steven Whitehouse
2013-07-30 12:40 ` [PATCH 7/9] xfs: " Tejun Heo
2013-07-30 18:13   ` Ben Myers
2013-07-30 12:40 ` [PATCH 8/9] ceph: " Tejun Heo
2013-07-30 12:40 ` [PATCH 9/9] l2tp: " Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1375188028-11910-1-git-send-email-tj@kernel.org \
    --to=tj@kernel.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shli@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox