From: Kalle Valo <kvalo@codeaurora.org>
To: <yintang@qti.qualcomm.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [TDLS PATCH V1 0/5] Add TDLS feature for ath10k
Date: Mon, 18 Sep 2017 15:43:28 +0300 [thread overview]
Message-ID: <87wp4wkwi7.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1505473420-22932-1-git-send-email-yintang@qti.qualcomm.com> (yintang@qti.qualcomm.com's message of "Fri, 15 Sep 2017 19:03:35 +0800")
<yintang@qti.qualcomm.com> writes:
> From: Yingying Tang <yintang@qti.qualcomm.com>
>
> This patchset is for Rome PCIE chip, it will not affect other hardware
>
> Yingying Tang (5):
> mac80211: Enable TDLS peer buffer STA feature
> ath10k: Enable TDLS peer buffer STA feature
> ath10k: Enable TDLS peer inactivity detection
> ath10k: Avoid to set WEP key for TDLS peer
> ath10k: Avoid to set WEP key for TDLS peer
There was a problem on patchwork.kernel.org over the weekend, but it
should be fixed now. Unfortunately your patches didn't make it to
patchwork, so please resend (as v2).
https://patchwork.kernel.org/project/linux-wireless/list/?state=*
--
Kalle Valo
next prev parent reply other threads:[~2017-09-18 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TDLS for ath10k>
2017-09-15 11:03 ` [TDLS PATCH V1 0/5] Add TDLS feature for ath10k yintang
2017-09-15 11:03 ` [TDLS PATCH V1 1/5] mac80211: Enable TDLS peer buffer STA feature yintang
2017-09-15 11:03 ` [TDLS PATCH V1 2/5] ath10k: " yintang
2017-09-15 11:03 ` [TDLS PATCH V1 3/5] ath10k: Enable TDLS peer inactivity detection yintang
2017-09-15 11:03 ` [TDLS PATCH V1 4/5] ath10k: Avoid to set WEP key for TDLS peer yintang
2017-09-18 12:43 ` Kalle Valo [this message]
2017-09-15 11:05 ` [TDLS PATCH V1 5/5] " 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=87wp4wkwi7.fsf@purkki.adurom.net \
--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