lly eedaf45f43 ble_mesh: Continue node info restore even if failure happens ... During BLE Mesh Provisioner initialization, the stack will restore the nodes information if settings storage is enabled. Previously when a failure happens (e.g. found the same uuid) during the restore procedure, the information of the following nodes will not be restored and error will be directly returned. But this will introduce some problem with user experience, because some newly provisioned nodes information will not be restored and Provisioner will not be able to control those nodes. So we change the operation here, when a failure happens during the restore procedure, Provisioner will only ignore the information of the current node and continue restoring other nodes information.		2020-04-30 11:47:12 +00:00
..
bluedroid	component/bt: fix don't dequeue the command queue after process the read_by_type_req(backport v3.3)	2020-03-31 16:45:57 +08:00
common	Component/bt :	2020-02-20 19:39:03 +08:00
esp_ble_mesh	ble_mesh: Continue node info restore even if failure happens	2020-04-30 11:47:12 +00:00
include	fix initializer order for BT_CONTROLLER_INIT_CONFIG_DEFAULT	2020-02-07 18:59:03 +08:00
lib@4d64d12dde	components/coex: Fix wakeup delay with DFS	2020-03-28 21:15:21 +08:00
test	bt: Fix unit tests build with CMake	2018-11-28 15:19:04 +08:00
bt.c	components/coex: Fix wakeup delay with DFS	2020-03-28 21:15:21 +08:00
CMakeLists.txt	Add support of NimBLE host in ESP-BLE-Mesh - v3.3	2020-02-13 12:33:23 +05:30
component.mk	Add support of NimBLE host in ESP-BLE-Mesh - v3.3	2020-02-13 12:33:23 +05:30
Kconfig	ble_mesh: Remove BLE_MESH_MAX_STORED_NODES option	2020-04-30 11:47:12 +00:00