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 v2 0/5] Mesh clean up
Date: Sat, 30 May 2020 21:41:23 -0700 [thread overview]
Message-ID: <20200531044128.16734-1-inga.stotland@intel.com> (raw)
v2: Restored some debug output related to model configuration state
**********
No functional changes: cleaned up debug output so that
hex print is not executed if debug is not enabled.
Style cleanup in net.c. Removed unused functions from net.h/net.c
Inga Stotland (5):
mesh: Helper packet print should depend on debug setting
mesh: Debug output clean up
mesh: Remove debug-only related callback for packet send
mesh: Clean up style in net.c
mesh: Remove unused functions from net.c
mesh/main.c | 3 +-
mesh/manager.c | 6 +-
mesh/mesh-io-generic.c | 3 +-
mesh/model.c | 52 +---
mesh/net.c | 572 +++++++++++------------------------------
mesh/net.h | 30 +--
mesh/pb-adv.c | 7 +-
mesh/prov-initiator.c | 2 +-
mesh/util.c | 11 +
mesh/util.h | 1 +
10 files changed, 182 insertions(+), 505 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-31 4:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 4:41 Inga Stotland [this message]
2020-05-31 4:41 ` [PATCH BlueZ v2 1/5] mesh: Helper packet print should depend on debug setting Inga Stotland
2020-05-31 4:41 ` [PATCH BlueZ v2 2/5] mesh: Debug output clean up Inga Stotland
2020-05-31 4:41 ` [PATCH BlueZ v2 3/5] mesh: Remove debug-only related callback for packet send Inga Stotland
2020-05-31 4:41 ` [PATCH BlueZ v2 4/5] mesh: Clean up style in net.c Inga Stotland
2020-05-31 5:08 ` [BlueZ,v2,4/5] " bluez.test.bot
2020-05-31 4:41 ` [PATCH BlueZ v2 5/5] mesh: Remove unused functions from net.c Inga Stotland
2020-06-01 17:25 ` [PATCH BlueZ v2 0/5] Mesh 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=20200531044128.16734-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).