From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, stable@kernel.org,
linux-wireless@vger.kernel.org, Paul Stewart <pstew@google.com>,
Amod Bodas <amod.bodas@atheros.com>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>,
Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] mac80211: fix rate_control_send_low warnings for delbas
Date: Wed, 29 Sep 2010 10:18:23 +0200 [thread overview]
Message-ID: <1285748303.3756.19.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100928222945.GB10932@tux>
On Tue, 2010-09-28 at 15:29 -0700, Luis R. Rodriguez wrote:
> Since we end up associated to two different APs at the same
> time to transmit to either AP consists of an offchannel
> operation but today we just lack the state machine to be able
> to do this properly so for now just drop those frames.
I really think that can be done more easily though. For one, clearly we
already have the warning, so we don't need more infrastructure to catch
such errors?! Also, this may end up hiding issues that we don't yet
understand, like the nullfunc one you were talking about. The delBA one
we now understand fully, so it makes more sense to simply suppress
sending delBA when we are going to disassociate by way of associating
with a new AP, no?
johannes
next prev parent reply other threads:[~2010-09-29 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 22:29 [PATCH] mac80211: fix rate_control_send_low warnings for delbas Luis R. Rodriguez
2010-09-28 23:02 ` Jouni Malinen
2010-09-28 23:58 ` Luis R. Rodriguez
2010-09-29 5:20 ` Vasanthakumar Thiagarajan
2010-09-29 7:24 ` Luis R. Rodriguez
2010-09-29 8:56 ` Vasanthakumar Thiagarajan
2010-09-29 17:16 ` Luis R. Rodriguez
2010-09-29 17:24 ` Johannes Berg
2010-09-29 8:18 ` Johannes Berg [this message]
2010-09-29 17:10 ` Luis R. Rodriguez
2010-09-29 17:25 ` Johannes Berg
2010-09-30 17:53 ` Luis R. Rodriguez
2010-10-01 20:07 ` Luis R. Rodriguez
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=1285748303.3756.19.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amod.bodas@atheros.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=pstew@google.com \
--cc=stable@kernel.org \
--cc=vasanth@atheros.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).