The kernel would previously return a hard coded instance value of 0x01
even when removing multiple advertising instances. This was ok as long
as we only had a single advertising instance but no longer makes sense
now that we allow for multiple advertising instances.
We therefore expect the mgmt API to return zero when multiple instances
have been removed. This corresponds to the semantics of the mgmt API
call made in the first place.
The corresponding test is updated to reflect that logic.
---
tools/mgmt-tester.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/mgmt-tester.c b/tools/mgmt-tester.c
index c0f58ce..4c62a6b 100644
--- a/tools/mgmt-tester.c
+++ b/tools/mgmt-tester.c
@@ -4465,8 +4465,8 @@ static const struct generic_data remove_advertising_success_2 = {
.send_param = remove_advertising_param_2,
.send_len = sizeof(remove_advertising_param_2),
.expect_status = MGMT_STATUS_SUCCESS,
- .expect_param = remove_advertising_param_1,
- .expect_len = sizeof(remove_advertising_param_1),
+ .expect_param = remove_advertising_param_2,
+ .expect_len = sizeof(remove_advertising_param_2),
.expect_alt_ev = MGMT_EV_ADVERTISING_REMOVED,
.expect_alt_ev_param = advertising_instance_param,
.expect_alt_ev_len = sizeof(advertising_instance_param),
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
