summaryrefslogtreecommitdiffstats
path: root/device/bluetooth/bluetooth_adapter_unittest.cc
diff options
context:
space:
mode:
authorkeybuk@chromium.org <keybuk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-02-27 20:43:20 +0000
committerkeybuk@chromium.org <keybuk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-02-27 20:43:20 +0000
commita4f56a0e5ad11fa145d7590dce2e31942fedd6fb (patch)
treebf74ebc455a857c1a314651b9f007b80dcdb05c9 /device/bluetooth/bluetooth_adapter_unittest.cc
parent07db4b3c95d4be48eeec3d4e4e209b196c76dd09 (diff)
downloadchromium_src-a4f56a0e5ad11fa145d7590dce2e31942fedd6fb.zip
chromium_src-a4f56a0e5ad11fa145d7590dce2e31942fedd6fb.tar.gz
chromium_src-a4f56a0e5ad11fa145d7590dce2e31942fedd6fb.tar.bz2
Add BluetoothDevice::PairingDelegate::AuthorizePairing
Now that we have the concept of a default pairing agent that may be used to handle incoming pairing requests we need to handle the case of authorizing a Just-Works pairing request from an unknown device. BUG=329583 TEST=device_unittests included Review URL: https://codereview.chromium.org/168603006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253919 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'device/bluetooth/bluetooth_adapter_unittest.cc')
-rw-r--r--device/bluetooth/bluetooth_adapter_unittest.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/device/bluetooth/bluetooth_adapter_unittest.cc b/device/bluetooth/bluetooth_adapter_unittest.cc
index c063bed..f4653c2 100644
--- a/device/bluetooth/bluetooth_adapter_unittest.cc
+++ b/device/bluetooth/bluetooth_adapter_unittest.cc
@@ -114,6 +114,7 @@ class TestPairingDelegate : public BluetoothDevice::PairingDelegate {
uint32 entered) OVERRIDE {}
virtual void ConfirmPasskey(BluetoothDevice* device,
uint32 passkey) OVERRIDE {}
+ virtual void AuthorizePairing(BluetoothDevice* device) OVERRIDE {}
};