linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Brian Gix <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: Re: [PATCH BlueZ v2 0/2] mesh: Fix inOOB and outOOB issues
Date: Sat, 16 Nov 2019 13:07:49 +0100	[thread overview]
Message-ID: <20191116120749.GC30589@aurel32.net> (raw)
In-Reply-To: <20191115231705.5596-1-brian.gix@intel.com>

On 2019-11-15 15:17, Brian Gix wrote:
> This patchset includes modification to both the Daemon and the
> mesh-cfgclient.  All of the inOOB and outOOB scenarios have been tested,
> and are working according to the Bluetooth Profile specification, for
> the Provisioner "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           |  12 +--
>  mesh/prov-initiator.c  |  69 +++++++++++++---
>  tools/mesh-cfgclient.c | 178 ++++++++++++++++++++++++++++++++++-------
>  tools/mesh-gatt/prov.c |   9 ++-
>  tools/mesh/agent.c     |  21 +++--
>  tools/mesh/agent.h     |   4 +-
>  6 files changed, 233 insertions(+), 60 deletions(-)

Thanks for the patches. I have just tried them and I confirm it fixes
output OOB with number. Output OOB with string still doesn't work. I
came up with this patch to fix it:

diff --git a/mesh/agent.c b/mesh/agent.c
index 623f2faf0..e5545d7f3 100644
--- a/mesh/agent.c
+++ b/mesh/agent.c
@@ -604,7 +604,7 @@ int mesh_agent_prompt_number(struct mesh_agent *agent, bool initiator,
 int mesh_agent_prompt_alpha(struct mesh_agent *agent, mesh_agent_key_cb_t cb,
 								void *user_data)
 {
-	return prompt_input(agent, "in-alpha", MESH_AGENT_REQUEST_IN_ALPHA,
+	return prompt_input(agent, "out-alpha", MESH_AGENT_REQUEST_OUT_ALPHA,
 							false, cb, user_data);
 }

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

      parent reply	other threads:[~2019-11-16 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 23:17 [PATCH BlueZ v2 0/2] mesh: Fix inOOB and outOOB issues Brian Gix
2019-11-15 23:17 ` [PATCH BlueZ v2 1/2] mesh: Fix inOOB and outOOB agent handling on prov initiate Brian Gix
2019-11-15 23:17 ` [PATCH BlueZ v2 2/2] tools/mesh-cfgclient: Add full support inOOB and outOOB Brian Gix
2019-11-16 12:07 ` Aurelien Jarno [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=20191116120749.GC30589@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=brian.gix@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).