From 091ff8929d5bfb58608f17b8bbb1f20e250bca52 Mon Sep 17 00:00:00 2001 From: Prasad Rane Date: Wed, 20 Jun 2018 12:35:28 +0530 Subject: [PATCH] Changed incorrect reference to Bluetooth Mesh specification The text quoted in the comment is in section 3.8.6 and not in 3.8.5. I am referring to Mesh Profile Bluetooth specifications v1.0 adopted on 2017-July-13 --- mesh/access/api/device_state_manager.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mesh/access/api/device_state_manager.h b/mesh/access/api/device_state_manager.h index b902c936..7d6a13b8 100644 --- a/mesh/access/api/device_state_manager.h +++ b/mesh/access/api/device_state_manager.h @@ -476,7 +476,7 @@ uint32_t dsm_subnet_get_all(mesh_key_index_t * p_key_list, uint32_t * p_count); * Adds a device key. * * @note "A device key is implicitly bound to all network keys." see Mesh Profile Bluetooth - * Specification v1.0, section 3.8.5. An exception to this is the provisioner who stores all the device + * Specification v1.0, section 3.8.6. An exception to this is the provisioner who stores all the device * keys of the other nodes, see section 5. * * @param[in] raw_unicast_addr Unicast address associated with this device key.