Hi Szymon, >>> It is no longer possible to send any data after disconnection. >>> Extra reference is taken for disconnect watch to allow users to drop >>> own reference in disconnect callback. >> >> I am not sure that is the best way to do it. I get the feeling that we might >> better have an internal bool that is tracking if we are >> connected/disconnected. Thoughts? > > You mean don't have a public HFP disconnect handler and just fail on write() > or use bool instead of io pointer for state tracking? we should still have a disconnect handler. However we should not take these extra reference and have these extra checks for something. I rather see us tracking the actual state of the IO and not trying to reference count our way into something insane. It is dangerous to have to many indirect reference counts. 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
