From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCHSET] workqueue: another assorted flush_scheduled_work() removals
Date: Fri, 24 Dec 2010 16:14:47 +0100 [thread overview]
Message-ID: <20101224151447.GC11419@htj.dyndns.org> (raw)
In-Reply-To: <1292172499-21633-1-git-send-email-tj@kernel.org>
On Sun, Dec 12, 2010 at 05:48:13PM +0100, Tejun Heo wrote:
> Hello,
>
> This is another set of patches to remove flush_scheduled_work() users.
>
> 0001-init-don-t-call-flush_scheduled_work-from-do_initcal.patch
> 0002-ioc4-use-static-work_struct-for-ioc4_load_modules.patch
> 0003-media-video-explicitly-flush-request_module-work.patch
> 0004-media-video-don-t-use-flush_scheduled_work.patch
> 0005-speedtch-don-t-abuse-struct-delayed_work.patch
> 0006-usb-don-t-use-flush_scheduled_work.patch
Merged into wq#for-next. Thanks.
--
tejun
prev parent reply other threads:[~2010-12-24 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 16:48 Tejun Heo
2010-12-12 16:48 ` [PATCH 1/6] init: don't call flush_scheduled_work() from do_initcalls() Tejun Heo
2010-12-12 16:48 ` [PATCH 2/6] ioc4: use static work_struct for ioc4_load_modules() Tejun Heo
2010-12-12 16:48 ` [PATCH 3/6] media/video: explicitly flush request_module work Tejun Heo
2010-12-12 16:48 ` [PATCH 4/6] media/video: don't use flush_scheduled_work() Tejun Heo
2010-12-12 16:48 ` [PATCH 5/6] speedtch: don't abuse struct delayed_work Tejun Heo
2010-12-16 21:30 ` Greg KH
2010-12-17 11:05 ` Tejun Heo
2010-12-12 16:48 ` [PATCH 6/6] usb: don't use flush_scheduled_work() Tejun Heo
2010-12-17 13:51 ` speedtch: don't abuse struct delayed_work Nicolas Kaiser
2010-12-18 11:58 ` Nicolas Kaiser
2010-12-18 16:32 ` [PATCH UPDATED 5/6] " Tejun Heo
2010-12-18 17:59 ` Nicolas Kaiser
2010-12-24 15:14 ` Tejun Heo [this message]
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=20101224151447.GC11419@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®