From: Johannes Berg <johannes@sipsolutions.net>
To: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
David Spinadel <david.spinadel@intel.com>
Subject: Re: [PATCH v5 1/3] cfg80211: support FTM responder configuration/statistics
Date: Mon, 01 Oct 2018 12:12:56 +0200 [thread overview]
Message-ID: <1538388776.3126.24.camel@sipsolutions.net> (raw)
In-Reply-To: <1537489811-5752-2-git-send-email-pradeepc@codeaurora.org>
On Thu, 2018-09-20 at 17:30 -0700, Pradeep Kumar Chitrapu wrote:
> Allow userspace to enable fine timing measurement responder
> functionality with configurable lci/civic parameters in AP mode.
> This can be done at AP start or changing beacon parameters.
>
> A new EXT_FEATURE flag is introduced for drivers to advertise
> the capability.
>
> Also nl80211 API support for retrieving statistics is added.
I applied this, but with some changes. Notably,
> /**
> + * cfg80211_ftm_responder_params - FTM responder parameters
I removed this struct, since it's no longer needed.
You do use it in mac80211, but since cfg80211 doesn't use it you should
declare it as ieee80211_ftm_respodner_params and use it in mac80211
only, I think.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-10-01 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 0:30 [PATCH v5 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu
2018-09-21 0:30 ` [PATCH v5 1/3] cfg80211: support FTM " Pradeep Kumar Chitrapu
2018-10-01 10:12 ` Johannes Berg [this message]
2018-09-21 0:30 ` [PATCH v5 2/3] mac80211: " Pradeep Kumar Chitrapu
2018-10-01 10:14 ` Johannes Berg
2018-09-21 0:30 ` [PATCH v5 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu
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=1538388776.3126.24.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=david.spinadel@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeepc@codeaurora.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