From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Don't go off-channel in work_work unless needed.
Date: Wed, 29 Sep 2010 22:05:29 +0200 [thread overview]
Message-ID: <1285790729.3756.37.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1285787159-9207-1-git-send-email-greearb@candelatech.com>
On Wed, 2010-09-29 at 12:05 -0700, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> If the work to be done is on the current active channel, then
> do not call the offchannel and return-to-channel logic.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
> v1 -> v2: Remove went_off_channel logic, and don't set
> tmp_channel if we're not going offchannel.
I briefly grepped through the source and am pretty sure this'll break a
few things in mlme.c and even the work-on-same-channel logic in
work.c...
johannes
next prev parent reply other threads:[~2010-09-29 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 19:05 [PATCH v2] mac80211: Don't go off-channel in work_work unless needed greearb
2010-09-29 20:05 ` Johannes Berg [this message]
2010-09-29 20:14 ` Ben Greear
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=1285790729.3756.37.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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).