From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Cc: "luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>
Subject: Re: [PATCH BlueZ 0/3] Save and restore mesh models pub/sub settings
Date: Mon, 11 Mar 2019 22:20:13 +0000 [thread overview]
Message-ID: <1552342809.29289.2.camel@intel.com> (raw)
In-Reply-To: <20190308225820.20561-1-inga.stotland@intel.com>
Patch set applied
On Fri, 2019-03-08 at 14:58 -0800, Inga Stotland wrote:
> This patch set implements the following:
> - Write updates of node model subscriptions to node config file
> - Write updates of node model publication settings to node config file
> - Correctly restore subscriptions and publications on daemon startup
>
> Inga Stotland (3):
> mesh: Add json config functions to save pub/sub updates
> mesh: Save model subscription updates to config file
> mesh: Store model publication settings in config file
>
> mesh/cfgmod-server.c | 104 +++++++++++++++-
> mesh/mesh-db.c | 282 ++++++++++++++++++++++++++++++++++++++++++-
> mesh/mesh-db.h | 15 ++-
> mesh/model.c | 22 ++--
> 4 files changed, 404 insertions(+), 19 deletions(-)
>
prev parent reply other threads:[~2019-03-11 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 22:58 [PATCH BlueZ 0/3] Save and restore mesh models pub/sub settings Inga Stotland
2019-03-08 22:58 ` [PATCH BlueZ 1/3] mesh: Add json config functions to save pub/sub updates Inga Stotland
2019-03-08 22:58 ` [PATCH BlueZ 2/3] mesh: Save model subscription updates to config file Inga Stotland
2019-03-08 22:58 ` [PATCH BlueZ 3/3] mesh: Store model publication settings in " Inga Stotland
2019-03-11 22:20 ` Gix, Brian [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=1552342809.29289.2.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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).