From: Tejun Heo <tj@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Warn about flush_scheduled_work()
Date: Mon, 21 Dec 2009 17:26:17 +0900 [thread overview]
Message-ID: <4B2F3129.1090803@kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0912161051160.2909-100000@iolanthe.rowland.org>
On 12/17/2009 12:52 AM, Alan Stern wrote:
> This patch (as1319) adds kerneldoc and a pointed warning to
> flush_scheduled_work().
>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Queued in local queue. Will commit to wq#for-next when and if it
opens. If cmwq gets nacked upstream. I'll route this one separately.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-12-21 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 21:33 Warn people about flush_scheduled_work() Alan Stern
2009-12-14 21:42 ` Oliver Neukum
2009-12-14 22:02 ` Alan Stern
2009-12-14 22:12 ` Oliver Neukum
2009-12-14 23:04 ` Alan Stern
2009-12-14 22:38 ` Tejun Heo
2009-12-14 23:14 ` Alan Stern
2009-12-14 23:25 ` Tejun Heo
2009-12-16 15:52 ` [PATCH] Warn " Alan Stern
2009-12-21 8:26 ` Tejun Heo [this message]
2010-02-12 8:47 ` 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=4B2F3129.1090803@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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