From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
yintang@qti.qualcomm.com, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [TDLS PATCH V3 1/5] mac80211: Enable TDLS peer buffer STA feature
Date: Tue, 19 Sep 2017 10:15:14 +0200 [thread overview]
Message-ID: <1505808914.3026.0.camel@sipsolutions.net> (raw)
In-Reply-To: <db428527-cb2b-5136-24c2-be2fca9e2407@broadcom.com> (sfid-20170919_095629_313381_9836835D)
On Tue, 2017-09-19 at 09:56 +0200, Arend van Spriel wrote:
>
> > --- a/include/net/cfg80211.h
> > +++ b/include/net/cfg80211.h
> > @@ -3249,6 +3249,8 @@ struct cfg80211_ops {
> > * beaconing mode (AP, IBSS, Mesh, ...).
> > * @WIPHY_FLAG_HAS_STATIC_WEP: The device supports static WEP key
> > installation
> > * before connection.
> > + * @WIPHY_FLAG_SUPPORT_TDLS_BUFFER_STA: Device support buffer STA
> > when TDLS is
> > + * established.
>
> If I am not mistaken no new wiphy flags are supposed to be added.
> Although this might be something not reported to user-space, right?
> Have a look at struct wiphy::ext_features.
I guess it should just be a HW flag in mac80211? Not sure why userspace
even needs to know.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-09-19 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TDLS for ath10k patchset v3>
2017-09-19 3:15 ` [TDLS PATCH V3 0/5] Add TDLS feature for ath10k yintang
2017-09-19 3:15 ` [TDLS PATCH V3 1/5] mac80211: Enable TDLS peer buffer STA feature yintang
2017-09-19 7:56 ` Arend van Spriel
2017-09-19 8:15 ` Johannes Berg [this message]
2017-09-19 9:55 ` Arend van Spriel
2017-09-19 3:15 ` [TDLS PATCH V3 2/5] ath10k: " yintang
2017-09-19 3:15 ` [TDLS PATCH V3 3/5] ath10k: Enable TDLS peer inactivity detection yintang
2017-09-19 3:15 ` [TDLS PATCH V3 4/5] ath10k: Avoid to set WEP key for TDLS peer yintang
2017-09-19 3:17 ` [TDLS PATCH V3 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=1505808914.3026.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--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