zephyr/net/bluetooth
Johan Hedberg a9404225e5 Bluetooth: Use NULL for "any" connection with bt_conn_lookup_state_le()
An all zeroes address is in principle not valid, but prototype devices
have been seen using it. To avoid false-positives with the
bt_conn_lookup_state_le() API use a NULL pointer rather than
BT_ADDR_LE_ANY to indicate that any connection in the specified state
is of interest.

Change-Id: I42a1946e47173b17be295b1b7e97a654dbdcdc6a
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-02-05 20:25:28 -05:00
..
att.c Bluetooth: UUID: Introduce new API 2016-02-05 20:25:28 -05:00
att.h
conn_internal.h
conn.c Bluetooth: Use NULL for "any" connection with bt_conn_lookup_state_le() 2016-02-05 20:25:28 -05:00
gatt_internal.h
gatt.c Bluetooth: UUID: Introduce new API 2016-02-05 20:25:28 -05:00
hci_core.c Bluetooth: Use NULL for "any" connection with bt_conn_lookup_state_le() 2016-02-05 20:25:28 -05:00
hci_core.h
Kconfig
keys.c
keys.h
l2cap_internal.h Bluetooth: L2CAP: Further simplify l2cap_chan_create_seg() 2016-02-05 20:25:28 -05:00
l2cap.c Bluetooth: L2CAP: Further simplify l2cap_chan_create_seg() 2016-02-05 20:25:28 -05:00
Makefile
smp_null.c
smp.c
smp.h
stack.h
uuid.c Bluetooth: Remove unused bt_uuid_copy() API 2016-02-05 20:25:28 -05:00