Hi Gianluca, > The following two patches fix a couple of regressions introduced with > the rfcomm tty_port conversion. > > The first patch restores the expected behaviour of the rfcomm port when > it's created with the flag RFCOMM_RELEASE_ONHUP. > > The second patch fixes a bug that affect userspace (ModemManager) when > the port is created with the flag RFCOMM_REUSE_DLC. > > Gianluca Anzolin (2): > rfcomm: release the port when the last user closes the tty > rfcomm: move the device under its parent if already connected > > net/bluetooth/rfcomm/tty.c | 68 ++++++++++++++++++++++++++-------------------- > 1 file changed, 39 insertions(+), 29 deletions(-) I applied both patches to bluetooth-next to expose them wider testing. I like to have them go through bluetooth-next first before we push them back into -stable. 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