From: Bastien Nocera <hadess@hadess.net>
To: andrey.zheregelya@dsr-company.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] doc/device-api.txt Information about D-Bus LastSeen property
Date: Tue, 02 Aug 2016 17:57:43 +0200 [thread overview]
Message-ID: <1470153463.21877.24.camel@hadess.net> (raw)
In-Reply-To: <20160802154059.24472-2-andrey.zheregelya@dsr-company.com>
On Tue, 2016-08-02 at 18:40 +0300, andrey.zheregelya@dsr-company.com
wrote:
> From: Andrey Zheregelya <andrey.zheregelya@dsr-company.com>
>
> ---
> doc/device-api.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/doc/device-api.txt b/doc/device-api.txt
> index 087efb9..6387a0c 100644
> --- a/doc/device-api.txt
> +++ b/doc/device-api.txt
> @@ -216,3 +216,11 @@ Properties string Address [readonly]
>
> Indicate whether or not service discovery
> has been
> resolved.
> +
> + bool LastSeen [readonly, experimantal]
> +
> + Unix time of last found device update.
> + Indicates if device is alive and reachable.
It's doesn't, really, until you apply heuristics to it. How do you plan
to use this?
> + Adapter should be in discovery mode.
> + Information about device's reachability is based
> + on advertisement packets.
next prev parent reply other threads:[~2016-08-02 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 15:40 [PATCH 1/2] device: LastSeen property for D-Bus interface andrey.zheregelya
2016-08-02 15:40 ` [PATCH 2/2] doc/device-api.txt Information about D-Bus LastSeen property andrey.zheregelya
2016-08-02 15:57 ` Bastien Nocera [this message]
2016-08-02 16:55 ` Andrey Zheregelya
2016-08-03 9:48 ` Luiz Augusto von Dentz
2016-08-03 12:32 ` Andrey Zheregelya
2016-08-03 12:46 ` Luiz Augusto von Dentz
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=1470153463.21877.24.camel@hadess.net \
--to=hadess@hadess.net \
--cc=andrey.zheregelya@dsr-company.com \
--cc=linux-bluetooth@vger.kernel.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