lly 713581ae87 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-26 06:25:08 +00:00
..
common	fix Kconfig use mistake cause some config not effect	2020-01-20 17:43:36 +08:00
controller	components/bt: Fix for HCI desync deadlock issue in BLE controller	2020-04-02 09:54:16 +00:00
esp_ble_mesh	ble_mesh: Continue node info restore even if failure happens	2020-04-26 06:25:08 +00:00
host	NimBLE: Reset master and slave states on host reset	2020-04-01 10:09:26 +00:00
include	components/bt: Fix A2DP stuck when BLE's interval is too small	2020-01-06 20:22:04 +08:00
test	test: declare requirements and include dirs private	2020-03-23 10:58:50 +08:00
CMakeLists.txt	ble_mesh: Support BLE advertising simultaneously	2020-04-02 01:03:25 +00:00
component.mk	NimBLE: Use dynamic buffers instead of static memory.	2020-01-23 00:55:51 +08:00
Kconfig	components/coex: Fix misspell in Kconfig	2020-02-19 11:41:03 +08:00
sdkconfig.rename	HFP AG Example	2019-11-27 13:35:35 +00:00