From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: nbd@nbd.name
Subject: Re: [RFC] mac80211: support non-data TXQs
Date: Tue, 20 Jun 2017 23:09:52 +0200 [thread overview]
Message-ID: <1497992992.11421.3.camel@sipsolutions.net> (raw)
In-Reply-To: <20170620210309.1193-1-johannes@sipsolutions.net> (sfid-20170620_230321_402397_A3FCC329)
On Tue, 2017-06-20 at 23:03 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Some drivers may want to also use the TXQ abstraction with
> non-data packets, so add a hardware flag to allow this.
Need to replace various ARRAY_SIZE(sta->txq) in ath9k/ath10k by
IEEE80211_NUM_TIDS.
johannes
next prev parent reply other threads:[~2017-06-20 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:03 [RFC] mac80211: support non-data TXQs Johannes Berg
2017-06-20 21:09 ` Johannes Berg [this message]
2017-06-21 4:19 ` Igor Mitsyanko
2017-06-21 7:09 ` Johannes Berg
2017-06-21 7:38 ` Igor Mitsyanko
2017-06-21 8:36 ` Johannes Berg
2017-06-21 8:37 ` Johannes Berg
2017-06-21 8:48 ` Arend van Spriel
2017-06-21 9:14 ` Johannes Berg
2017-06-21 9:24 ` Johannes Berg
2017-06-21 9:45 ` 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=1497992992.11421.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).