From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: don't duplicate station QoS capability data
Date: Thu, 24 Jul 2014 12:50:24 +0200 [thread overview]
Message-ID: <1406199024.14675.9.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1406198192-29442-1-git-send-email-johannes@sipsolutions.net> (sfid-20140724_123645_348075_85F44270)
On Thu, 2014-07-24 at 12:36 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> We currently track the QoS capability twice: for all peer stations
> in the WLAN_STA_WME flag, and for any clients associated to an AP
> interface separately for drivers in the sta->sta.wme field.
>
> Remove the WLAN_STA_WME flag and track the capability only in the
> driver-visible field, getting rid of the limitation that the field
> is only valid in AP mode.
Err, fixing mesh compilation ...
johannes
prev parent reply other threads:[~2014-07-24 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 10:36 [PATCH] mac80211: don't duplicate station QoS capability data Johannes Berg
2014-07-24 10:50 ` Johannes Berg [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=1406199024.14675.9.camel@jlt4.sipsolutions.net \
--to=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 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).