From: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
To: David Howells <dhowells@redhat.com>,
Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joseph Qi <joseph.qi@huawei.com>,
"Norton.Zhu" <norton.zhu@huawei.com>,
Jun Piao <piaojun@huawei.com>, xuejiufei <xuejiufei@huawei.com>
Cc: ocfs2-devel@oss.oracle.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: [PATCH 0/9] Remove deprecated create_singlethread_workqueue
Date: Tue, 30 Aug 2016 23:13:47 +0530 [thread overview]
Message-ID: <cover.1472578959.git.bhaktipriya96@gmail.com> (raw)
This patch set removes deprecated create_singlethread_workqueue
usages in fs/.
Bhaktipriya Shridhar (9):
fs/afs/vlocation: Remove deprecated create_singlethread_workqueue
fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue
fs/afs/callback: Remove deprecated create_singlethread_workqueue
fs/afs/flock: Remove deprecated create_singlethread_workqueue
fs/ocfs2/dlmfs: Remove deprecated create_singlethread_workqueue
fs/ocfs2/cluster: Remove deprecated create_singlethread_workqueue
fs/ocfs2/super: Remove deprecated create_singlethread_workqueue
fs/ocfs2/dlm: Remove deprecated create_singlethread_workqueue
fs/nfsd/nfs4callback: Remove deprecated create_singlethread_workqueue
fs/afs/callback.c | 4 ++--
fs/afs/flock.c | 4 ++--
fs/afs/rxrpc.c | 2 +-
fs/afs/vlocation.c | 4 ++--
fs/nfsd/nfs4callback.c | 2 +-
fs/ocfs2/cluster/tcp.c | 2 +-
fs/ocfs2/dlm/dlmdomain.c | 2 +-
fs/ocfs2/dlmfs/dlmfs.c | 2 +-
fs/ocfs2/super.c | 2 +-
9 files changed, 12 insertions(+), 12 deletions(-)
--
2.1.4
next reply other threads:[~2016-08-30 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 17:43 Bhaktipriya Shridhar [this message]
2016-08-30 17:44 ` [PATCH 1/9] fs/afs/vlocation: Remove deprecated create_singlethread_workqueue Bhaktipriya Shridhar
2016-08-30 17:44 ` [PATCH 2/9] fs/afs/rxrpc: " Bhaktipriya Shridhar
2016-08-30 17:45 ` [PATCH 3/9] fs/afs/callback: " Bhaktipriya Shridhar
2016-08-30 17:45 ` [PATCH 4/9] fs/afs/flock: " Bhaktipriya Shridhar
2016-08-31 14:28 ` Tejun Heo
2016-08-30 17:45 ` [PATCH 5/9] fs/ocfs2/dlmfs: " Bhaktipriya Shridhar
2016-08-30 17:46 ` [PATCH 6/9] fs/ocfs2/cluster: " Bhaktipriya Shridhar
2016-08-30 17:46 ` [PATCH 7/9] fs/ocfs2/super: " Bhaktipriya Shridhar
2016-08-30 17:46 ` [PATCH 8/9] fs/ocfs2/dlm: " Bhaktipriya Shridhar
2016-08-31 14:29 ` Tejun Heo
2016-08-30 17:47 ` [PATCH 9/9] fs/nfsd/nfs4callback: " Bhaktipriya Shridhar
2016-08-31 14:29 ` Tejun Heo
2016-08-30 19:36 ` [Ocfs2-devel] [PATCH 0/9] " David Howells
2016-08-30 19:36 ` David Howells
2016-08-30 19:58 ` Bhaktipriya Shridhar
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=cover.1472578959.git.bhaktipriya96@gmail.com \
--to=bhaktipriya96@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@huawei.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=mhocko@suse.com \
--cc=norton.zhu@huawei.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=piaojun@huawei.com \
--cc=tj@kernel.org \
--cc=vdavydov@virtuozzo.com \
--cc=xuejiufei@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.