Hi Johan, > Even though our side requests authentication, the original action that > caused it may be remotely triggered, such as an incoming L2CAP or RFCOMM > connect request. To track this information introduce a new hci_conn flag > called HCI_CONN_AUTH_INITIATOR. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > include/net/bluetooth/hci_core.h | 1 + > net/bluetooth/hci_conn.c | 3 +++ > net/bluetooth/hci_event.c | 5 +++++ > 3 files changed, 9 insertions(+) patch has been applied to bluetooth-next tree. Regards Marcel -- 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
