From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, inga.stotland@intel.com,
michal.lowas-rzechonek@silvair.com
Subject: [PATCH BlueZ v3 0/1] Add Mesh Provisioning Loop-Back mechanism
Date: Fri, 10 Jan 2020 17:38:55 -0800 [thread overview]
Message-ID: <20200111013856.32675-1-brian.gix@intel.com> (raw)
Version 3 fixed logic flaw which is supposed to prevent to sessions with
same roll being loop-back to each other, or more than one loop-back
session.
Version 2 centralizes the loop-back mechanism
Cosmetic changes reversed, as they added nothing important to the
functionality.
Brian Gix (1):
mesh: Implement provisioning loop-back
mesh/pb-adv.c | 163 ++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 130 insertions(+), 33 deletions(-)
--
2.21.1
next reply other threads:[~2020-01-11 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 1:38 Brian Gix [this message]
2020-01-11 1:38 ` [PATCH BlueZ v3 1/1] mesh: Implement provisioning loop-back Brian Gix
2020-01-11 6:34 ` Michał Lowas-Rzechonek
2020-01-11 7:19 ` Michał Lowas-Rzechonek
2020-01-11 15:24 ` Gix, Brian
2020-01-11 6:32 ` [PATCH BlueZ v3 0/1] Add Mesh Provisioning Loop-Back mechanism Michał Lowas-Rzechonek
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=20200111013856.32675-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.