From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Jouni Malinen <jouni@qca.qualcomm.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath9k: Enable U-APSD AP mode support
Date: Tue, 18 Feb 2014 23:18:27 +0100 [thread overview]
Message-ID: <5303DC33.5050105@openwrt.org> (raw)
In-Reply-To: <1392750354.5438.8.camel@jlt4.sipsolutions.net>
On 2014-02-18 20:05, Johannes Berg wrote:
> On Tue, 2014-02-18 at 20:41 +0200, Jouni Malinen wrote:
>> mac80211 handles the actual operations, so ath9k can just indicate
>> support for this. Based on initial tests, this combination seems to
>> work fine.
>
> I believe this is not true with aggregation sessions.
Why not? Block Ack Window handling is handled by
.release_buffered_frames just fine (and tested with PS-Poll).
- Felix
next prev parent reply other threads:[~2014-02-18 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 18:41 [PATCH] ath9k: Enable U-APSD AP mode support Jouni Malinen
2014-02-18 19:05 ` Johannes Berg
2014-02-18 22:18 ` Felix Fietkau [this message]
2014-02-19 9:48 ` 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=5303DC33.5050105@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).