linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ v4 00/10] Mesh Config Server clean up
Date: Wed,  5 Aug 2020 10:44:46 -0700	[thread overview]
Message-ID: <20200805174456.49342-1-inga.stotland@intel.com> (raw)

v4 - Further fixes in handling Key Refresh Phase Set message

*******************
 v3 - address Brian's comments
 
*******************
This patch set groups functionality by config messages.
Also, fixes the cases where malformed messages should be  silently
ignored and the situations when incorrect error status
is sent in response.

Inga Stotland (10):
  mesh: Clean up handling of config subscription messages
  mesh: Clean up handling of config model binding messages
  mesh: Clean up handling of config node identity message
  mesh: Clean up handling of config publication messages
  mesh: Clean up handling of config net and app key messages
  mesh: Clean up handling of config relay messages
  mesh: Clean up handling of config poll timeout message
  mesh: Clean up handling of config net transmit messages
  mesh: Clean up handling of config KR phase messages
  mesh: Refactor heartbeat pub/sub

 mesh/cfgmod-server.c    | 1196 +++++++++++++++++----------------------
 mesh/cfgmod.h           |    2 +-
 mesh/mesh-config-json.c |   12 +-
 mesh/mesh-config.h      |    6 +-
 mesh/mesh-defs.h        |    3 +
 mesh/model.c            |  234 ++++----
 mesh/model.h            |   21 +-
 mesh/net.c              |  326 +++++++----
 mesh/net.h              |   54 +-
 mesh/node.h             |    4 -
 10 files changed, 912 insertions(+), 946 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-08-05 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 17:44 Inga Stotland [this message]
2020-08-05 17:44 ` [PATCH BlueZ v4 01/10] mesh: Clean up handling of config subscription messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 02/10] mesh: Clean up handling of config model binding messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 03/10] mesh: Clean up handling of config node identity message Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 04/10] mesh: Clean up handling of config publication messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 05/10] mesh: Clean up handling of config net and app key messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 06/10] mesh: Clean up handling of config relay messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 07/10] mesh: Clean up handling of config poll timeout message Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 08/10] mesh: Clean up handling of config net transmit messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 09/10] mesh: Clean up handling of config KR phase messages Inga Stotland
2020-08-05 17:44 ` [PATCH BlueZ v4 10/10] mesh: Refactor heartbeat pub/sub Inga Stotland

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=20200805174456.49342-1-inga.stotland@intel.com \
    --to=inga.stotland@intel.com \
    --cc=brian.gix@intel.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).