Bluetooth: Remove incorrect check for BDADDR_BREDR address type
The Add Remote OOB Data mgmt command should allow data to be passed for LE as well. This patch removes a left-over check for BDADDR_BREDR that should not be there anymore. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
parent
5d57e7964c
commit
484aabc1c4
|
@ -3672,14 +3672,6 @@ static int add_remote_oob_data(struct sock *sk, struct hci_dev *hdev,
|
|||
u8 *rand192, *hash192;
|
||||
u8 status;
|
||||
|
||||
if (cp->addr.type != BDADDR_BREDR) {
|
||||
err = cmd_complete(sk, hdev->id,
|
||||
MGMT_OP_ADD_REMOTE_OOB_DATA,
|
||||
MGMT_STATUS_INVALID_PARAMS,
|
||||
&cp->addr, sizeof(cp->addr));
|
||||
goto unlock;
|
||||
}
|
||||
|
||||
if (bdaddr_type_is_le(cp->addr.type)) {
|
||||
rand192 = NULL;
|
||||
hash192 = NULL;
|
||||
|
|
Loading…
Reference in a new issue