From: Tim Hockin <thockin@sun.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: calling flush_scheduled_work()
Date: Fri, 12 Mar 2004 16:20:27 -0800 [thread overview]
Message-ID: <20040313002026.GB1333@sun.com> (raw)
In-Reply-To: <20040312152747.0b3f74d3.akpm@osdl.org>
On Fri, Mar 12, 2004 at 03:27:47PM -0800, Andrew Morton wrote:
> Seems simple enough to fix the workqueue code to handle this situation.
Indeed. I should have done that myself. Thanks.
> Wanna test this for me?
Works for me.
--
Tim Hockin
Sun Microsystems, Linux Software Engineering
thockin@sun.com
All opinions are my own, not Sun's
next prev parent reply other threads:[~2004-03-13 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 20:58 calling flush_scheduled_work() Tim Hockin
2004-03-12 22:00 ` Trond Myklebust
2004-03-12 22:38 ` Tim Hockin
2004-03-12 23:19 ` Trond Myklebust
2004-03-12 23:27 ` Tim Hockin
2004-03-12 23:27 ` Andrew Morton
2004-03-13 0:20 ` Tim Hockin [this message]
2004-03-13 1:17 ` Trond Myklebust
2004-03-13 2:12 ` Andrew Morton
2004-03-13 2:24 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-03-13 11:45 Stefan Rompf
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=20040313002026.GB1333@sun.com \
--to=thockin@sun.com \
--cc=akpm@osdl.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