linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Lior David <liord@codeaurora.org>, linux-wireless@vger.kernel.org
Cc: Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
	luca@coelho.fi, Etan Cohen <etancohen@google.com>,
	Roy Want <roywant@google.com>,
	Arend Van Spriel <arend.vanspriel@broadcom.com>,
	Franky Lin <franky.lin@broadcom.com>
Subject: Re: [RFC v2] cfg80211: add peer measurement with FTM API
Date: Fri, 12 Oct 2018 12:02:29 +0200	[thread overview]
Message-ID: <1539338549.3141.8.camel@sipsolutions.net> (raw)
In-Reply-To: <1538942338.2928.21.camel@sipsolutions.net> (sfid-20181007_215915_302871_10D82211)

On Sun, 2018-10-07 at 21:58 +0200, Johannes Berg wrote:
> 
> > > + * @partial: indicates that this is a partial result for this type
> > 
> > Is partial set to false for the last result of this measurement type? This may
> > be useful, for example if requesting multiple measurement types, user space can
> > start processing one measurement type before the entire session is completed.
> 
> Yes, that was the intent, e.g. for multiple FTM bursts, but I see how
> this might be misleading at this level. I'll clarify the documentation
> (and probably over in nl80211.h as well)

Actually, I changed my mind - I'll add a "final" bit as well, so
"partial" will be set on all of them.

johannes

      parent reply	other threads:[~2018-10-12 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 13:35 [RFC v2] cfg80211: add peer measurement with FTM API Johannes Berg
2018-10-07 19:39 ` Lior David
2018-10-07 19:58   ` Johannes Berg
2018-10-09 14:40     ` Lior David
2018-10-11 10:05       ` Johannes Berg
2018-10-17 10:05         ` Lior David
2018-10-17 10:09           ` Johannes Berg
2018-10-12 10:02     ` Johannes Berg [this message]

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=1539338549.3141.8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=etancohen@google.com \
    --cc=franky.lin@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liord@codeaurora.org \
    --cc=luca@coelho.fi \
    --cc=pradeepc@codeaurora.org \
    --cc=roywant@google.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).