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> |
||
|---|---|---|
| .. | ||
| application_development | ||
| arch | ||
| benchmarks | ||
| bluetooth | ||
| boards | ||
| boot | ||
| bsim | ||
| cmake | ||
| crypto | ||
| drivers | ||
| integration/kernel | ||
| kconfig | ||
| kernel | ||
| lib | ||
| misc | ||
| modules | ||
| net | ||
| posix | ||
| robot | ||
| subsys | ||
| unit | ||
| ztest | ||
| test_config.yaml | ||