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 0/3] Code re-org and clean up
Date: Mon, 13 Jul 2020 16:05:25 -0700	[thread overview]
Message-ID: <20200713230528.107948-1-inga.stotland@intel.com> (raw)

This patch set is part of the on-going  clean up effort that targets some
of more convoluted areas of meshd source code.
The patchset provides better functional separation, smaller function
granularity and better memory handling.

Inga Stotland (3):
  mesh: Use static array to hold config server response
  mesh: Add size checks for every opcode in config server
  mesh: move model functionality out of node.c to model.c

 mesh/cfgmod-server.c    |  99 ++++++-----
 mesh/cfgmod.h           |   4 +-
 mesh/mesh-config-json.c |   5 +-
 mesh/model.c            | 359 +++++++++++++++++++++++++++++++++-------
 mesh/model.h            |  32 ++--
 mesh/node.c             | 286 ++++----------------------------
 6 files changed, 403 insertions(+), 382 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-07-13 23:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 23:05 Inga Stotland [this message]
2020-07-13 23:05 ` [PATCH BlueZ 1/3] mesh: Use static array to hold config server response Inga Stotland
2020-07-13 23:05 ` [PATCH BlueZ 2/3] mesh: Add size checks for every opcode in config server Inga Stotland
2020-07-13 23:05 ` [PATCH BlueZ 3/3] mesh: move model functionality out of node.c to model.c Inga Stotland
2020-07-16 17:20 ` [PATCH BlueZ 0/3] Code re-org and clean up 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=20200713230528.107948-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).