All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
	ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
	david.spinadel@intel.com
Subject: Re: [PATCH v3 0/3] support ftm responder configuration/statistics
Date: Thu, 06 Sep 2018 18:15:17 +0300	[thread overview]
Message-ID: <877ejy7j3u.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1536215640.4015.0.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 06 Sep 2018 08:34:00 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Wed, 2018-09-05 at 18:01 -0700, Pradeep Kumar Chitrapu wrote:
>> Currently ftm_responder parameter in hostapd.conf is only used for fine
>> timing measurement (FTM) capability advertisement and actual control of
>> the functionality is with low-level device/driver. This leads to confusion
>> to the user when the capability advertisement is different from actual FTM
>> responder functionality.
>> 
>> For example, FTM responder capability advertisement is set to 'enabled',
>> but the functionality is disabled or not supported by the driver.
>> 
>> The patch set allows userspace to enable FTM responder functionality
>> with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER
>> with configurable lci/civic ocation parameters. Also extended feature flag
>> is added for the drivers to advertise the support. Setting the flag to
>> enable FTM responder would imply that AP responds to all FTM requests.
>> Default is considered to be disabled.
>> 
>> changes in V3:
>>  - fixed the ambiguous ftm responder disable case to be not supported
>
> For reasons unknown to me, this patchset made it neither to the list
> nor, consequently, patchwork. Please resend.

Actually patch 3 made it:

https://patchwork.kernel.org/patch/10590115/

But it didn't get the rest as it says "Untitled series #15763".
Patchwork was timing out for me quite heavily so in that way I'm not
surprised that patches are getting lost :(

-- 
Kalle Valo

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
	linux-wireless@vger.kernel.org, david.spinadel@intel.com,
	ath10k@lists.infradead.org
Subject: Re: [PATCH v3 0/3] support ftm responder configuration/statistics
Date: Thu, 06 Sep 2018 18:15:17 +0300	[thread overview]
Message-ID: <877ejy7j3u.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1536215640.4015.0.camel@sipsolutions.net> (Johannes Berg's message of "Thu, 06 Sep 2018 08:34:00 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> On Wed, 2018-09-05 at 18:01 -0700, Pradeep Kumar Chitrapu wrote:
>> Currently ftm_responder parameter in hostapd.conf is only used for fine
>> timing measurement (FTM) capability advertisement and actual control of
>> the functionality is with low-level device/driver. This leads to confusion
>> to the user when the capability advertisement is different from actual FTM
>> responder functionality.
>> 
>> For example, FTM responder capability advertisement is set to 'enabled',
>> but the functionality is disabled or not supported by the driver.
>> 
>> The patch set allows userspace to enable FTM responder functionality
>> with the addition of new Netlink flag attribute NL80211_ATTR_FTM_RESPONDER
>> with configurable lci/civic ocation parameters. Also extended feature flag
>> is added for the drivers to advertise the support. Setting the flag to
>> enable FTM responder would imply that AP responds to all FTM requests.
>> Default is considered to be disabled.
>> 
>> changes in V3:
>>  - fixed the ambiguous ftm responder disable case to be not supported
>
> For reasons unknown to me, this patchset made it neither to the list
> nor, consequently, patchwork. Please resend.

Actually patch 3 made it:

https://patchwork.kernel.org/patch/10590115/

But it didn't get the rest as it says "Untitled series #15763".
Patchwork was timing out for me quite heavily so in that way I'm not
surprised that patches are getting lost :(

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2018-09-06 19:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  1:01 [PATCH v3 0/3] support ftm responder configuration/statistics Pradeep Kumar Chitrapu
2018-09-06  1:01 ` Pradeep Kumar Chitrapu
2018-09-06  1:01 ` [PATCH v3 1/3] cfg80211: support FTM " Pradeep Kumar Chitrapu
2018-09-06  1:01 ` [PATCH v3 2/3] mac80211: " Pradeep Kumar Chitrapu
2018-09-06  1:01   ` Pradeep Kumar Chitrapu
2018-09-06  1:01 ` [PATCH v3 3/3] ath10k: Add support to configure ftm responder role Pradeep Kumar Chitrapu
2018-09-06  1:01   ` Pradeep Kumar Chitrapu
2018-09-06  6:34 ` [PATCH v3 0/3] support ftm responder configuration/statistics Johannes Berg
2018-09-06  6:34   ` Johannes Berg
2018-09-06 15:15   ` Kalle Valo [this message]
2018-09-06 15:15     ` Kalle Valo
2018-09-06 16:08     ` Johannes Berg
2018-09-06 16:08       ` Johannes Berg
2018-09-06 16:18       ` Kalle Valo
2018-09-06 16:18         ` Kalle Valo
2018-09-06 17:06 Pradeep Kumar Chitrapu
2018-09-06 17:06 ` Pradeep Kumar Chitrapu
2018-09-06 19:58 ` Johannes Berg
2018-09-06 19:58   ` Johannes Berg
2018-09-07  9:23   ` Arend van Spriel
2018-09-07  9:23     ` Arend van Spriel
2018-09-06 21:11 Pradeep Kumar Chitrapu
2018-09-06 21:11 ` 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=877ejy7j3u.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=david.spinadel@intel.com \
    --cc=johannes@sipsolutions.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.