From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ] mesh: Fix handling of Config Relay Set message
Date: Fri, 16 Aug 2019 09:36:27 +0200 [thread overview]
Message-ID: <20190816073627.18123-1-michal.lowas-rzechonek@silvair.com> (raw)
---
mesh/cfgmod-server.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mesh/cfgmod-server.c b/mesh/cfgmod-server.c
index dbed7e03f..55cc8e9eb 100644
--- a/mesh/cfgmod-server.c
+++ b/mesh/cfgmod-server.c
@@ -872,8 +872,7 @@ static bool cfg_srv_pkt(uint16_t src, uint32_t dst, uint16_t unicast,
count = (pkt[1] >> 5) + 1;
interval = ((pkt[1] & 0x1f) + 1) * 10;
- node_relay_mode_set(node, !!pkt[0], pkt[1]>>5,
- pkt[1] & 0x1f);
+ node_relay_mode_set(node, !!pkt[0], count, interval);
/* Fall Through */
case OP_CONFIG_RELAY_GET:
--
2.19.1
reply other threads:[~2019-08-16 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190816073627.18123-1-michal.lowas-rzechonek@silvair.com \
--to=michal.lowas-rzechonek@silvair.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).