From: Kalle Valo <kvalo@codeaurora.org>
To: yintang@qti.qualcomm.com
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [v7,2/5] ath10k: Enable TDLS peer buffer STA feature
Date: Thu, 29 Mar 2018 09:00:59 +0000 (UTC) [thread overview]
Message-ID: <20180329090059.994F660C54@smtp.codeaurora.org> (raw)
In-Reply-To: <1508835074-3384-3-git-send-email-yintang@qti.qualcomm.com>
yintang@qti.qualcomm.com wrote:
> Enable TDLS peer buffer STA feature.
> QCA6174 firmware(version: WLAN.RM.4.4) support TDLS peer buffer STA,
> it reports this capability through wmi service map in wmi service ready
> event. Set related parameter in TDLS WMI command to enable this feature.
>
> Signed-off-by: Yingying Tang <yintang@qti.qualcomm.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
4 patches applied to ath-next branch of ath.git, thanks.
802ca335496e ath10k: enable TDLS peer buffer STA feature
4c9f8d114660 ath10k: enable TDLS peer inactivity detection
c3816c9ee12c ath10k: avoid to set WEP key for TDLS peer
9cdd00575029 ath10k: fix TDLS peer TX data failure issue on encryped AP
--
https://patchwork.kernel.org/patch/10023753/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-03-29 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TDLS for ath10k patch v7>
2017-10-24 8:51 ` [PATCH v7 0/5] Add TDLS feature for ath10k yintang
2017-10-24 8:51 ` [PATCH v7 1/5] mac80211: Enable TDLS peer buffer STA feature yintang
2017-10-24 8:51 ` [PATCH v7 2/5] ath10k: " yintang
2017-10-27 9:25 ` [v7,2/5] " Kalle Valo
2018-03-29 9:00 ` Kalle Valo [this message]
2017-10-24 8:51 ` [PATCH v7 3/5] ath10k: Enable TDLS peer inactivity detection yintang
2018-03-28 15:41 ` [v7,3/5] " Kalle Valo
2017-10-24 8:51 ` [PATCH v7 4/5] ath10k: Avoid to set WEP key for TDLS peer yintang
2017-10-24 8:52 ` [PATCH v7 5/5] ath10k: Fix TDLS peer TX data failure issue on encryped AP yintang
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=20180329090059.994F660C54@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yintang@qti.qualcomm.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).