From: Michael Buesch <mb@bu3sch.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Pavel Roskin <proski@gnu.org>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
users@rt2x00.serialmonkey.com
Subject: Re: [PATCH] rt2x00dev: cancel all work on disconnect
Date: Thu, 30 Jul 2009 20:58:30 +0200 [thread overview]
Message-ID: <200907302058.30699.mb@bu3sch.de> (raw)
In-Reply-To: <200907302045.15400.IvDoorn@gmail.com>
On Thursday 30 July 2009 20:45:15 Ivo van Doorn wrote:
> Hi,
>
> I assume fixes the bug Michael reported on Linux-wireless yesterday?
I didn't test that, yet, but the patch looks sane anyway.
> The patch looks good, but I have some minor modification request:
>
> On Wednesday 29 July 2009, Pavel Roskin wrote:
> > Signed-off-by: Pavel Roskin <proski@gnu.org>
> > ---
> > drivers/net/wireless/rt2x00/rt2x00dev.c | 7 +++++++
> > 1 files changed, 7 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/net/wireless/rt2x00/rt2x00dev.c b/drivers/net/wireless/rt2x00/rt2x00dev.c
> > index 658a63b..66b303b 100644
> > --- a/drivers/net/wireless/rt2x00/rt2x00dev.c
> > +++ b/drivers/net/wireless/rt2x00/rt2x00dev.c
> > @@ -888,6 +888,13 @@ void rt2x00lib_remove_dev(struct rt2x00_dev *rt2x00dev)
> > clear_bit(DEVICE_STATE_PRESENT, &rt2x00dev->flags);
> >
> > /*
> > + * Cancel all work.
> > + */
> > + rt2x00link_stop_tuner(rt2x00dev);
>
> This one isn't needed. rt2x00lib_disable_radio() is doing this.
>
> > + cancel_work_sync(&rt2x00dev->filter_work);
> > + cancel_work_sync(&rt2x00dev->intf_work);
>
> Could you move these 2 until after the call to rt2x00lib_disable_radio()?
>
> > + /*
> > * Disable radio.
> > */
> > rt2x00lib_disable_radio(rt2x00dev);
>
> Thanks,
>
> Ivo
>
>
--
Greetings, Michael.
prev parent reply other threads:[~2009-07-30 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 20:07 [PATCH] rt2x00dev: cancel all work on disconnect Pavel Roskin
2009-07-30 18:45 ` Ivo van Doorn
2009-07-30 18:58 ` Michael Buesch [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=200907302058.30699.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
--cc=users@rt2x00.serialmonkey.com \
/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).