Hi Marcel, > the struct io is an internal detail to bt_att. I do not follow the comment regards to upper layer. The input into bt_att_new will be a file descriptor. > What I meant was that, upon receiving the timeout callback, should whoever created the bt_att be responsible for explicitly destroying the connection by calling bt_att_unref (which will internally free the struct io)? Just thinking out loud. > So what I thinking is that we just do io_destroy(att->io) and then att->io = NULL. > In the disconnect case, is this safe to do from directly inside the disconnect callback given to io_set_disconnect_handler? Thanks, Arman -- 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
