From: Kalle Valo <kvalo@codeaurora.org>
To: Mathy Vanhoef <Mathy.Vanhoef@kuleuven.be>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
Mathy Vanhoef <Mathy.Vanhoef@kuleuven.be>
Subject: Re: [PATCH 5/5] ath9k_htc: adhere to the DONT_REORDER transmit flag
Date: Wed, 9 Dec 2020 07:05:33 +0000 (UTC) [thread overview]
Message-ID: <20201209070533.CCCA4C43461@smtp.codeaurora.org> (raw)
In-Reply-To: <20201104061823.197407-6-Mathy.Vanhoef@kuleuven.be>
Mathy Vanhoef <Mathy.Vanhoef@kuleuven.be> wrote:
> Assure that frames with the fixed order flag are not reordered
> relative to each other. This is accomplished by transmitting them
> using a fixed priority independent of their QoS field.
>
> Signed-off-by: Mathy Vanhoef <Mathy.Vanhoef@kuleuven.be>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
8a71f34bb251 ath9k_htc: adhere to the DONT_REORDER transmit flag
--
https://patchwork.kernel.org/project/linux-wireless/patch/20201104061823.197407-6-Mathy.Vanhoef@kuleuven.be/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-12-09 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:18 [PATCH 0/5] mac80211: implement DONT_REORDER radiotap flag Mathy Vanhoef
2020-11-04 6:18 ` [PATCH 1/5] mac80211: add radiotap flag to assure frames are not reordered Mathy Vanhoef
2020-11-04 6:18 ` [PATCH 2/5] mac80211: adhere to Tx control flag that prevents frame reordering Mathy Vanhoef
2020-11-04 6:18 ` [PATCH 3/5] mac80211: don't overwrite QoS TID of injected frames Mathy Vanhoef
2020-11-04 6:18 ` [PATCH 4/5] mac80211: assure that certain drivers adhere to DONT_REORDER flag Mathy Vanhoef
2020-11-04 6:18 ` [PATCH 5/5] ath9k_htc: adhere to the DONT_REORDER transmit flag Mathy Vanhoef
2020-12-09 7:05 ` Kalle Valo [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=20201209070533.CCCA4C43461@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Mathy.Vanhoef@kuleuven.be \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=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).