From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: "Gix, Brian" <brian.gix@intel.com>
Cc: "jakub.witowski@silvair.com" <jakub.witowski@silvair.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH 1/2] mesh: Add sequence nr getter to the doc
Date: Tue, 14 Jan 2020 16:40:12 +0100 [thread overview]
Message-ID: <20200114154012.gixnyhceabg2lrsp@mlowasrzechonek2133> (raw)
In-Reply-To: <1382d00407f6c7836f7983e374d6c504931f6e9e.camel@intel.com>
Hi Brian,
On 01/14, Gix, Brian wrote:
> > + 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?
There are 2 use cases:
- debugging and monitoring RPL behaviour
- we'd like to add another API to increase the sequence number - this
is useful when you Import() a node from another database and would
like to bump its sequence number up to a previously known value, so
that the rest of the network can talk to it
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
next prev parent reply other threads:[~2020-01-14 15:40 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 ` [PATCH 1/2] mesh: Add sequence nr getter to the doc Gix, Brian
2020-01-14 15:40 ` Michał Lowas-Rzechonek [this message]
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=20200114154012.gixnyhceabg2lrsp@mlowasrzechonek2133 \
--to=michal.lowas-rzechonek@silvair.com \
--cc=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).