5f59b35b42
This change makes sure that when a call to `bt_id_set_scan_own_addr` is sucessful, i.e., the return value is 0, the `own_addr_type` will be set by the `bt_id_set_scan_own_addr`. Not setting the `own_addr_type` in a successful call to `bt_id_set_scan_own_addr` causes, for example, the `start_le_scan_ext` method in `scan.c` to use an uninitialized `own_addr_type`. Eventually this results in an unexpected failure further down in `start_le_scan_ext`, when sending HCI command to controller with an uninitialized `own_addr_type`. Signed-off-by: Erik Sandgren <erik.sandgren@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| bt_br_oob_get_local | ||
| bt_id_add | ||
| bt_id_adv_random_addr_check | ||
| bt_id_create | ||
| bt_id_del | ||
| bt_id_delete | ||
| bt_id_get | ||
| bt_id_init | ||
| bt_id_read_public_addr | ||
| bt_id_reset | ||
| bt_id_scan_random_addr_check | ||
| bt_id_set_adv_own_addr | ||
| bt_id_set_adv_private_addr | ||
| bt_id_set_adv_random_addr | ||
| bt_id_set_create_conn_own_addr | ||
| bt_id_set_private_addr | ||
| bt_id_set_scan_own_addr | ||
| bt_le_ext_adv_oob_get_local | ||
| bt_le_oob_get_local | ||
| bt_le_oob_get_sc_data | ||
| bt_le_oob_set_legacy_tk | ||
| bt_le_oob_set_sc_data | ||
| bt_lookup_id_addr | ||
| bt_setup_public_id_addr | ||
| bt_setup_random_id_addr | ||
| mocks | ||
| testing_common_defs.h | ||