summaryrefslogtreecommitdiff
path: root/include/net/bluetooth/rfcomm.h
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2013-10-13 10:34:02 -0700
committerJohan Hedberg <johan.hedberg@intel.com>2013-10-13 21:11:23 +0300
commit94a86df01082557e2de45865e538d7fb6c46231c (patch)
treef943d91c76a0d386705bbee5df1eea21670fd2c6 /include/net/bluetooth/rfcomm.h
parenteea963641bf548bda164b92aa20ccda56c5cf349 (diff)
Bluetooth: Store RFCOMM address information in its own socket structure
The address information of RFCOMM sockets should be stored in its own socket structure. Trying to generalize them is not helpful since different transports have different address types. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Diffstat (limited to 'include/net/bluetooth/rfcomm.h')
-rw-r--r--include/net/bluetooth/rfcomm.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/net/bluetooth/rfcomm.h b/include/net/bluetooth/rfcomm.h
index 7afd4199d6b6..3588f48bfd35 100644
--- a/include/net/bluetooth/rfcomm.h
+++ b/include/net/bluetooth/rfcomm.h
@@ -300,6 +300,8 @@ struct rfcomm_conninfo {
struct rfcomm_pinfo {
struct bt_sock bt;
+ bdaddr_t src;
+ bdaddr_t dst;
struct rfcomm_dlc *dlc;
u8 channel;
u8 sec_level;