From: Nagaraj D R <nagaraj.dr@samsung.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 1/1] mesh: Fix invalid netkey index in appkey add/delete
Date: Tue, 3 Dec 2019 15:23:27 +0530 [thread overview]
Message-ID: <1575366807-7878-1-git-send-email-nagaraj.dr@samsung.com> (raw)
In-Reply-To: CGME20191203095335epcas5p2f42315a8d7d9a081afa929f96bb66356@epcas5p2.samsung.com
8 LSbs of netkey index should be packed into the first octet
---
tools/mesh-gatt/config-client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/mesh-gatt/config-client.c b/tools/mesh-gatt/config-client.c
index 5e6374f..ed31c67 100644
--- a/tools/mesh-gatt/config-client.c
+++ b/tools/mesh-gatt/config-client.c
@@ -591,7 +591,7 @@ static void cmd_app_key(int argc, char *argv[], uint32_t opcode)
return bt_shell_noninteractive_quit(EXIT_FAILURE);
}
- msg[n++] = net_idx & 0xf;
+ msg[n++] = net_idx & 0xff;
msg[n++] = ((net_idx >> 8) & 0xf) |
((app_idx << 4) & 0xf0);
msg[n++] = app_idx >> 4;
--
2.7.4
next parent reply other threads:[~2019-12-03 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191203095335epcas5p2f42315a8d7d9a081afa929f96bb66356@epcas5p2.samsung.com>
2019-12-03 9:53 ` Nagaraj D R [this message]
2019-12-03 18:49 ` [PATCH 1/1] mesh: Fix invalid netkey index in appkey add/delete 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=1575366807-7878-1-git-send-email-nagaraj.dr@samsung.com \
--to=nagaraj.dr@samsung.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