From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: inga.stotland@intel.com, brian.gix@intel.com
Subject: [PATCH BlueZ v2] mesh: Fix bug with adding more than one app key
Date: Mon, 11 Mar 2019 10:10:59 -0700 [thread overview]
Message-ID: <20190311171059.12298-1-brian.gix@intel.com> (raw)
Fixed problem where if the appKeys array already exists, that new add
key requests were rejected.
---
mesh/mesh-db.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mesh/mesh-db.c b/mesh/mesh-db.c
index 2dc13cd65..d5d19d52f 100644
--- a/mesh/mesh-db.c
+++ b/mesh/mesh-db.c
@@ -533,8 +533,6 @@ bool mesh_db_app_key_add(json_object *jobj, uint16_t net_idx, uint16_t app_idx,
char buf[5];
json_object_object_get_ex(jobj, "appKeys", &jarray);
- if (jarray)
- return false;
if (jarray)
jentry = get_key_object(jarray, app_idx);
--
2.14.5
next reply other threads:[~2019-03-11 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 17:10 Brian Gix [this message]
2019-03-11 22:21 ` [PATCH BlueZ v2] mesh: Fix bug with adding more than one app key 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=20190311171059.12298-1-brian.gix@intel.com \
--to=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).