From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "aurelien@aurel32.net" <aurelien@aurel32.net>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v3 0/2] mesh: Fix inOOB and outOOB issues
Date: Wed, 20 Nov 2019 16:14:20 +0000 [thread overview]
Message-ID: <f3bac4dc1aee3d242a0ba09d69b43bea7474b391.camel@intel.com> (raw)
In-Reply-To: <20191119215227.27730-1-brian.gix@intel.com>
Patch-set applied
On Tue, 2019-11-19 at 13:52 -0800, Brian Gix wrote:
> Version 3 of this patch-set addresses problem found by Aurelien
> regarding the action string passed to the external agent collecting
> alpha-numeric strings on "out-alpha" prompts.
>
> This fix therefore now differentiates alphanumeric collection due to
> "in-alpha" (acceptor role) from "out-alpha" (initiator role).
>
> Brian Gix (1):
> mesh: Fix inOOB and outOOB agent handling on prov initiate
>
> Inga Stotland (1):
> tools/mesh-cfgclient: Add full support inOOB and outOOB
>
> mesh/agent.c | 28 ++++---
> mesh/agent.h | 4 +-
> mesh/prov-acceptor.c | 2 +-
> mesh/prov-initiator.c | 71 +++++++++++++---
> tools/mesh-cfgclient.c | 178 ++++++++++++++++++++++++++++++++++-------
> tools/mesh-gatt/prov.c | 9 ++-
> tools/mesh/agent.c | 21 +++--
> tools/mesh/agent.h | 4 +-
> 8 files changed, 249 insertions(+), 68 deletions(-)
>
prev parent reply other threads:[~2019-11-20 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 21:52 [PATCH BlueZ v3 0/2] mesh: Fix inOOB and outOOB issues Brian Gix
2019-11-19 21:52 ` [PATCH BlueZ v3 1/2] mesh: Fix inOOB and outOOB agent handling on prov initiate Brian Gix
2019-11-19 21:52 ` [PATCH BlueZ v3 2/2] tools/mesh-cfgclient: Add full support inOOB and outOOB Brian Gix
2019-11-20 16:14 ` Gix, Brian [this message]
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=f3bac4dc1aee3d242a0ba09d69b43bea7474b391.camel@intel.com \
--to=brian.gix@intel.com \
--cc=aurelien@aurel32.net \
--cc=inga.stotland@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