Bluetooth: Unify remote OOB data functions
There's no need to duplicate code for the 192 vs 192+256 variants of the OOB data functions. This is also helpful to pave the way to support LE SC OOB data where only 256 bit data is provided. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:

committed by
Marcel Holtmann

parent
903b71c78d
commit
81328d5cca
@@ -3599,7 +3599,8 @@ static int add_remote_oob_data(struct sock *sk, struct hci_dev *hdev,
|
||||
}
|
||||
|
||||
err = hci_add_remote_oob_data(hdev, &cp->addr.bdaddr,
|
||||
cp->hash, cp->rand);
|
||||
cp->hash, cp->rand,
|
||||
NULL, NULL);
|
||||
if (err < 0)
|
||||
status = MGMT_STATUS_FAILED;
|
||||
else
|
||||
@@ -3619,9 +3620,9 @@ static int add_remote_oob_data(struct sock *sk, struct hci_dev *hdev,
|
||||
goto unlock;
|
||||
}
|
||||
|
||||
err = hci_add_remote_oob_ext_data(hdev, &cp->addr.bdaddr,
|
||||
cp->hash192, cp->rand192,
|
||||
cp->hash256, cp->rand256);
|
||||
err = hci_add_remote_oob_data(hdev, &cp->addr.bdaddr,
|
||||
cp->hash192, cp->rand192,
|
||||
cp->hash256, cp->rand256);
|
||||
if (err < 0)
|
||||
status = MGMT_STATUS_FAILED;
|
||||
else
|
||||
|
Reference in New Issue
Block a user