From: Tejun Heo <tj@kernel.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2.6.36-rc7] cifs: cancel_delayed_work() + flush_scheduled_work() -> cancel_delayed_work_sync()
Date: Tue, 19 Oct 2010 18:15:21 +0200 [thread overview]
Message-ID: <4CBDC419.8060909@kernel.org> (raw)
In-Reply-To: <20101019121319.16f06b76@corrin.poochiereds.net>
Hello,
On 10/19/2010 06:13 PM, Jeff Layton wrote:
> On Tue, 19 Oct 2010 17:55:54 +0200
> Tejun Heo <tj@kernel.org> wrote:
>
>> flush_scheduled_work() is going away.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>> ---
>> fs/cifs/cifs_dfs_ref.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> Index: work/fs/cifs/cifs_dfs_ref.c
>> ===================================================================
>> --- work.orig/fs/cifs/cifs_dfs_ref.c
>> +++ work/fs/cifs/cifs_dfs_ref.c
>> @@ -44,8 +44,7 @@ static void cifs_dfs_expire_automounts(s
>> void cifs_dfs_release_automount_timer(void)
>> {
>> BUG_ON(!list_empty(&cifs_dfs_automount_list));
>> - cancel_delayed_work(&cifs_dfs_automount_task);
>> - flush_scheduled_work();
>> + cancel_delayed_work_sync(&cifs_dfs_automount_task);
>> }
>>
>> /**
>
> Looks like a better way to do this anyhow.
>
> Reviewed-by: Jeff Layton <jlayton@redhat.com>
Yeah, way faster too. It would be best to route this patch through
cifs tree but I can push it through wq tree too. Just let me know.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-10-19 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 15:55 [PATCH v2.6.36-rc7] cifs: cancel_delayed_work() + flush_scheduled_work() -> cancel_delayed_work_sync() Tejun Heo
2010-10-19 16:13 ` Jeff Layton
2010-10-19 16:15 ` Tejun Heo [this message]
2010-10-19 18:22 ` Steve French
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=4CBDC419.8060909@kernel.org \
--to=tj@kernel.org \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.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