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>
This commit is contained in:
parent
eea963641b
commit
94a86df010
2 changed files with 17 additions and 13 deletions
|
|
@ -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;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue