[PATCH 0/3 v1] Fix stop discovery not handled if discovery state is STARTING

Jaganath Kanakkassery <jaganath.k@xxxxxxxxxxx> · Thu, 06 Dec 2012 16:35:55 +0530

If user calls stop_discovery when the discovery state is STARTING, then it fails.
In this scenario discovery will continue. 

This patch handles stop_discovery even if state is STARTING

Jaganath Kanakkassery (3):
  Bluetooth: Rename stop_discovery_failed() to
    stop_discovery_complete()
  Bluetooth: Move discovery state check inside hci_dev_lock()
  Bluetooth: Fix stop discovery while in STARTING state

 include/net/bluetooth/hci_core.h |    3 ++-
 net/bluetooth/hci_core.c         |    9 ++++++++-
 net/bluetooth/hci_event.c        |   28 +++++++++++++++++++---------
 net/bluetooth/mgmt.c             |   15 ++++++++++-----
 4 files changed, 39 insertions(+), 16 deletions(-)

-- 
1.7.9.5

--
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