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 0/3] Allow to reattach with new composition data
Date: Wed, 22 Jan 2020 19:02:30 +0100 [thread overview]
Message-ID: <20200122180230.h57v3snd6x7uingg@kynes> (raw)
In-Reply-To: <56b3aa902dee18a45e91d826344085cf1fb3ecca.camel@intel.com>
On 01/20, Gix, Brian wrote:
> On Mon, 2020-01-20 at 17:11 +0100, Jakub Witowski wrote:
> > This patch allows the application to modify the CID, PID, VID and
> > CRPL in the composition data.
>
> This will require some discussion. Currently we are planning at
> *least* to make CRPL entirely under the control of
> bluetooth-mesh.conf, because this has a significant daemon impact.
Alright, but at the moment the daemon accepts whatever the application
specifies. The proposed patch doesn't change that, so maybe let's keep
it that way until a dedicated change in CRPL behaviour lands?
--
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-22 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 16:11 [PATCH 0/3] Allow to reattach with new composition data Jakub Witowski
2020-01-20 16:11 ` [PATCH 1/3] mesh: use static node_comp instead of the pointer Jakub Witowski
2020-01-20 16:11 ` [PATCH 2/3] mesh: add composition data setter Jakub Witowski
2020-01-20 16:11 ` [PATCH 3/3] mesh: allow to reattach with new composition data Jakub Witowski
2020-01-20 17:17 ` [PATCH 0/3] Allow " Gix, Brian
2020-01-21 10:59 ` jakub.witowski
2020-01-21 18:21 ` Stotland, Inga
2020-01-21 20:05 ` Michał Lowas-Rzechonek
2020-01-22 13:53 ` jakub.witowski
2020-01-22 18:02 ` Michał Lowas-Rzechonek [this message]
2020-01-22 18:03 ` Michał 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=20200122180230.h57v3snd6x7uingg@kynes \
--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