From: Tejun Heo <tj@kernel.org>
To: linux-scsi@vger.kernel.org, James.Bottomley@suse.de,
fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org,
Eric.Moore@lsi.com, dgilbert@interlog.com
Subject: [PATCHSET] scsi: don't use flush_scheduled_work()
Date: Tue, 21 Dec 2010 16:01:55 +0100 [thread overview]
Message-ID: <1292943721-4519-1-git-send-email-tj@kernel.org> (raw)
Hello,
This patchset removes the use of flush_scheduled_work() from scsi
drivers and contains the following six patches.
0001-scsi-remove-flush_scheduled_work-usages.patch
0002-scsi-pm8001-simplify-workqueue-usage.patch
0003-fcoe-use-dedicated-workqueue-instead-of-system_wq.patch
0004-fusion-don-t-use-flush_scheduled_work.patch
0005-scsi-remove-bogus-use-of-struct-execute_work-in-sg.patch
0006-scsi-don-t-use-execute_in_process_context.patch
The patches are on top of the current scsi-misc-2.6#master +
wq#for-2.6.38[1]. The latter is necessary for commit c8efcc25
(workqueue: allow chained queueing during destruction) as 0003 and
0006 depend on destroy_workqueue() handling chained works correctly.
James, how does 0006 look to you now? If you think it's acceptable,
please feel free to pull from wq#for-2.6.38, the branch is stable and
won't be rebased.
Thank you.
--
tejun
[1] git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-2.6.38
next reply other threads:[~2010-12-21 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 15:01 Tejun Heo [this message]
2010-12-21 15:01 ` [PATCH 1/6] scsi: remove flush_scheduled_work() usages Tejun Heo
2010-12-21 15:01 ` [PATCH 2/6] scsi: pm8001: simplify workqueue usage Tejun Heo
2010-12-21 15:01 ` [PATCH 3/6] fcoe: use dedicated workqueue instead of system_wq Tejun Heo
2010-12-21 15:01 ` [PATCH 4/6] fusion: don't use flush_scheduled_work() Tejun Heo
2011-01-10 7:30 ` Desai, Kashyap
2011-01-11 15:13 ` Tejun Heo
2010-12-21 15:02 ` [PATCH 5/6] scsi: remove bogus use of struct execute_work in sg Tejun Heo
2010-12-21 15:02 ` [PATCH 6/6] scsi: don't use execute_in_process_context() 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=1292943721-4519-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@suse.de \
--cc=dgilbert@interlog.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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;
as well as URLs for NNTP newsgroup(s).