summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/mgmt.c
diff options
context:
space:
mode:
authorJohan Hedberg <johan.hedberg@intel.com>2014-10-26 20:33:47 +0100
committerMarcel Holtmann <marcel@holtmann.org>2014-12-03 16:51:20 +0100
commit81328d5cca7e1cff6296a63a3c1b671d09ddb3ee (patch)
tree92656f21f12461a8ca4f101e82b3a3c2ebb83651 /net/bluetooth/mgmt.c
parent903b71c78d56af56a5f4d53a8dbef8032d1949bf (diff)
downloadop-kernel-dev-81328d5cca7e1cff6296a63a3c1b671d09ddb3ee.zip
op-kernel-dev-81328d5cca7e1cff6296a63a3c1b671d09ddb3ee.tar.gz
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>
Diffstat (limited to 'net/bluetooth/mgmt.c')
-rw-r--r--net/bluetooth/mgmt.c9
1 files changed, 5 insertions, 4 deletions
diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
index 6e81653..0d92ba9 100644
--- a/net/bluetooth/mgmt.c
+++ b/net/bluetooth/mgmt.c
@@ -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
OpenPOWER on IntegriCloud