From: Johannes Berg <johannes@sipsolutions.net>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mac80211: support non-data TXQs
Date: Wed, 21 Jun 2017 10:36:16 +0200 [thread overview]
Message-ID: <1498034176.4955.2.camel@sipsolutions.net> (raw)
In-Reply-To: <b4a28e42-bc8c-57ff-0bc0-e0b1eed6a6c1@quantenna.com>
On Wed, 2017-06-21 at 00:38 -0700, Igor Mitsyanko wrote:
>
> > That's standard for management frames, I really didn't think that'd
> > need any comment?
>
> You're right, for some reason I thought about "null data" frames
> instead of "no data" frames.
Well, the next patch actually does put those there as well :)
johannes
next prev parent reply other threads:[~2017-06-21 8:36 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
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 [this message]
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=1498034176.4955.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=igor.mitsyanko.os@quantenna.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).