From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: some fixes for ieee80211_do_stop while suspend
Date: Mon, 18 Mar 2013 10:30:47 +0100 [thread overview]
Message-ID: <20130318093046.GA1458@redhat.com> (raw)
In-Reply-To: <1363362270.8656.25.camel@jlt4.sipsolutions.net>
On Fri, Mar 15, 2013 at 04:44:30PM +0100, Johannes Berg wrote:
> On Mon, 2013-03-11 at 18:01 +0100, Stanislaw Gruszka wrote:
> > Is possible that we close interface while we are suspended, that
> > can result warning like below (and some others similar):
>
> > Patch try to avoid calling most of drv callbacks when stopping interface
> > while suspended.
>
> try :-)
It basically fix my test case, but I'm not sure if there are no other
problems, not covered by this test.
> I really wonder if there's not a better solution ... I'll think about it
> a bit.
I thought about 2 solutions:
1) Do not drv_remove_interface() and drv_stop() on suspend. Need to
check and possibly rewrite drivers to work with that, so this is not
preferred solution for me.
2) Add "if (local->started && !local->suspended) check in some drv_
callbacks, IOW silently ignore callbacks when suspended. This looks
as even worse hack than this patch.
Stanislaw
next prev parent reply other threads:[~2013-03-18 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 17:01 [PATCH 1/2] mac80211: some fixes for ieee80211_do_stop while suspend Stanislaw Gruszka
2013-03-11 17:01 ` [PATCH 2/2] mac80211: fixes for virtual monitor add/remove on suspend Stanislaw Gruszka
2013-03-11 17:07 ` Stanislaw Gruszka
2013-03-12 10:32 ` [PATCH 2/2 v2] " Stanislaw Gruszka
2013-03-15 15:44 ` [PATCH 1/2] mac80211: some fixes for ieee80211_do_stop while suspend Johannes Berg
2013-03-18 9:30 ` Stanislaw Gruszka [this message]
2013-03-22 21:14 ` Johannes Berg
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=20130318093046.GA1458@redhat.com \
--to=sgruszka@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.