From: Luciano Coelho <coelho@ti.com>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: use freezable workqueue for netstack_work
Date: Mon, 27 Jun 2011 14:08:56 +0300 [thread overview]
Message-ID: <1309172936.30221.30.camel@cumari> (raw)
In-Reply-To: <1307440246-22062-1-git-send-email-eliad@wizery.com>
On Tue, 2011-06-07 at 12:50 +0300, Eliad Peller wrote:
> When resuming (after wowlan), we want the rx packets (which is
> usually the wake-up packet itself) to be passed to mac80211 only
> after the resume notifier was completed, and mac80211 is up and
> running (otherwise, the packets will be dropped).
>
> By enqueueing the netstack_work to a freezable workqueue, we can
> guarantee the rx processing to occur only after mac80211 was resumed.
>
> Signed-off-by: Eliad Peller <eliad@wizery.com>
> Signed-off-by: Ido Yariv <ido@wizery.com>
> ---
Applied. Thanks!
--
Cheers,
Luca.
prev parent reply other threads:[~2011-06-27 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 9:50 [PATCH] wl12xx: use freezable workqueue for netstack_work Eliad Peller
2011-06-27 11:08 ` Luciano Coelho [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=1309172936.30221.30.camel@cumari \
--to=coelho@ti.com \
--cc=eliad@wizery.com \
--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 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).