From: "Gix, Brian" <brian.gix@intel.com>
To: "jakub.witowski@silvair.com" <jakub.witowski@silvair.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH 1/2] mesh: Add sequence nr getter to the doc
Date: Tue, 14 Jan 2020 14:50:12 +0000 [thread overview]
Message-ID: <1382d00407f6c7836f7983e374d6c504931f6e9e.camel@intel.com> (raw)
In-Reply-To: <20200114114914.25868-1-jakub.witowski@silvair.com>
Hi Jakub,
On Tue, 2020-01-14 at 12:49 +0100, Jakub Witowski wrote:
> ---
> doc/mesh-api.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
> index ebff8492a..d83c68bdc 100644
> --- a/doc/mesh-api.txt
> +++ b/doc/mesh-api.txt
> @@ -441,6 +441,11 @@ Properties:
>
> This property contains unicast addresses of node's elements.
>
> + uint32 SequenceNumber [read-only]
> +
> + This property may be read at any time to determine the
> + sequence number.
> +
Is there a use case justification for exposing this value? Why an Application would need this?
> Mesh Provisioning Hierarchy
> ============================
> Service org.bluez.mesh
next prev parent reply other threads:[~2020-01-14 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 11:49 [PATCH 1/2] mesh: Add sequence nr getter to the doc Jakub Witowski
2020-01-14 11:49 ` [PATCH 2/2] mesh: Add sequence nr getter code Jakub Witowski
2020-01-14 14:50 ` Gix, Brian [this message]
2020-01-14 15:40 ` [PATCH 1/2] mesh: Add sequence nr getter to the doc Michał Lowas-Rzechonek
2020-01-14 16:39 ` Gix, Brian
2020-01-14 16:53 ` michal.lowas-rzechonek
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=1382d00407f6c7836f7983e374d6c504931f6e9e.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=jakub.witowski@silvair.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;
as well as URLs for NNTP newsgroup(s).