From: reinette chatre <reinette.chatre@intel.com>
To: TJ <ubuntu@tjworld.net>
Cc: Huaxu Wan <huaxu.wan@linux.intel.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwl3945: Don't queue rfkill_poll work when module is exiting
Date: Thu, 26 Mar 2009 12:39:03 -0700 [thread overview]
Message-ID: <1238096343.25000.57.camel@rc-desk> (raw)
In-Reply-To: <1237955476.4388.6.camel@hephaestion>
On Tue, 2009-03-24 at 21:31 -0700, TJ wrote:
> On Wed, 2009-03-25 at 11:41 +0800, Huaxu Wan wrote:
> > Hi,
> >
> > This issue is confirmed here too. But during compile, there is warning about
> > cancel_work_sync(), cancel_delayed_work_sync() should be used instead.
> >
> > And, without the modification in iwl3945_rfkill_poll() and
> > iwl3945_mac_stop(), just with one line cancel_delayed_work_sync(), this issue
> > is also fixed in my testing.
>
> Originally I did try adding just cancel_delayed_work_sync() although I
> put it immediately following:
>
> iwl3945_rfkill_unregister(priv);
> cancel_delayed_work(&priv->rfkill_poll);
>
> Wondered why that didn't work and hunted down the unnecessary calls to
> queue_delayed_work() that were causing the issue and made them
> conditional on STATUS_EXIT_PENDING.
>
> Then I decided to be absolutely sure and moved cancel_delayed_work()
> further down and for some reason mis-used cancel_work_sync() instead of
> cancel_delayed_work_sync() - not paying attention I guess!
Sounds like this can be done in one line ... could you please resubmit?
Thanks
Reinette
next prev parent reply other threads:[~2009-03-26 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 15:44 iwl3945: Don't queue rfkill_poll work when module is exiting TJ
2009-03-24 17:51 ` Helmut Schaa
2009-03-24 21:22 ` TJ
2009-03-25 3:41 ` Huaxu Wan
2009-03-25 4:31 ` TJ
2009-03-26 19:39 ` reinette chatre [this message]
2009-04-02 22:36 ` reinette chatre
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=1238096343.25000.57.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=helmut.schaa@googlemail.com \
--cc=huaxu.wan@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ubuntu@tjworld.net \
/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).