Hi Marcel, On Sun, Oct 13, 2013, Marcel Holtmann wrote: > With the effort of abstracting the L2CAP socket from the underlying > L2CAP channel it is important to store the source and destination > address information directly in the L2CAP channel structure. > > Direct access to the HCI connection address information is not > possible since they might not be avaiable at L2CAP channel > creation time. The address information will be updated when > the underlying BR/EDR or LE connection status changes. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > include/net/bluetooth/l2cap.h | 2 ++ > net/bluetooth/l2cap_core.c | 61 +++++++++++++++++-------------------------- > net/bluetooth/l2cap_sock.c | 6 ++--- > 3 files changed, 29 insertions(+), 40 deletions(-) Applied to bluetooth-next. Thanks. Johan -- 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
