From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, michal.lowas-rzechonek@silvair.com,
jakub.witowski@silvair.com,
Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ 00/10 v3] mesh: Configuration storage re-org
Date: Sun, 14 Jul 2019 16:23:10 -0700 [thread overview]
Message-ID: <20190714232320.20921-1-inga.stotland@intel.com> (raw)
+ rebase off the tip
This set of patches introduces the notion of generic mesh-config API
that allows the daemon to be agnostic of the underlying node configuration
directory layout and the format of the file(s) in which node configuration
is saved.
Currently, the daemon supports only JSON-based configuration format.
It is expected that other configuration formats may be added in future.
As a result of these changes, storage.c and storage.h are obsolete
and are removed.
Inga Stotland (10):
mesh: Move network config setup from storage.c to node.c
mesh: Rename mesh-db.c to mesh-config-json.c
mesh: Change mesh_db prefix to mesh_config
mesh: Move load from storage functionality into node.c
mesh: Confine dependency on json-c to mesh-config-json.c
mesh: Replace storage_save_config with mesh_config_save_config
mesh: Use mesh_config APIs to store node configuration
mesh: Manage node config directory in mesh-config
mesh: Create or re-use a node storage directory for keyring
mesh: Rename mesh_config_srv_init() to cfgmod_server_init()
Makefile.mesh | 3 +-
mesh/appkey.c | 19 +-
mesh/cfgmod-server.c | 31 +-
mesh/cfgmod.h | 2 +-
mesh/keyring.c | 36 +-
mesh/{mesh-db.c => mesh-config-json.c} | 1071 +++++++++++++++++-------
mesh/mesh-config.h | 172 ++++
mesh/mesh-db.h | 157 ----
mesh/mesh.c | 15 +-
mesh/mesh.h | 1 +
mesh/model.c | 23 +-
mesh/net.c | 26 +-
mesh/node.c | 224 +++--
mesh/node.h | 13 +-
mesh/storage.c | 656 ---------------
mesh/storage.h | 51 --
mesh/util.c | 39 +-
mesh/util.h | 1 +
18 files changed, 1219 insertions(+), 1321 deletions(-)
rename mesh/{mesh-db.c => mesh-config-json.c} (58%)
create mode 100644 mesh/mesh-config.h
delete mode 100644 mesh/mesh-db.h
delete mode 100644 mesh/storage.c
delete mode 100644 mesh/storage.h
--
2.21.0
next reply other threads:[~2019-07-14 23:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 23:23 Inga Stotland [this message]
2019-07-14 23:23 ` [PATCH BlueZ 01/10 v3] mesh: Move network config setup from storage.c to node.c Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 02/10 v3] mesh: Rename mesh-db.c to mesh-config-json.c Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 03/10 v3] mesh: Change mesh_db prefix to mesh_config Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 04/10 v3] mesh: Move load from storage functionality into node.c Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 05/10 v3] mesh: Confine dependency on json-c to mesh-config-json.c Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 06/10 v3] mesh: Replace storage_save_config with mesh_config_save_config Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 07/10 v3] mesh: Use mesh_config APIs to store node configuration Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 08/10 v3] mesh: Manage node config directory in mesh-config Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 09/10 v3] mesh: Create or re-use a node storage directory for keyring Inga Stotland
2019-07-14 23:23 ` [PATCH BlueZ 10/10 v3] mesh: Rename mesh_config_srv_init() to cfgmod_server_init() Inga Stotland
2019-07-15 8:07 ` [PATCH BlueZ 00/10 v3] mesh: Configuration storage re-org Michał Lowas-Rzechonek
2019-07-15 16:59 ` Stotland, Inga
2019-07-15 22:27 ` Gix, Brian
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=20190714232320.20921-1-inga.stotland@intel.com \
--to=inga.stotland@intel.com \
--cc=brian.gix@intel.com \
--cc=jakub.witowski@silvair.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.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).