Wednesday, February 12, 2014, 12:06:44 PM, you wrote: > Monday, February 10, 2014, 11:09:38 PM, you wrote: >> Hi Peter, >>> This patch series addresses a number of previously unknown issues >>> with the RFCOMM tty device implementation, in addition to >>> addressing the locking regression recently reported [1]. >>> >>> As Gianluca suggested and I agree, this series first reverts >>> 3 of the 4 patches of 3.14-rc1 for bluetooth/rfcomm/tty.c. >> so for 3.14 we should revert 3 patches. And then the other 21 are intended for 3.15 merge window. >> I realize that we still have to deal with some breakage, but we do not want regressions and I clearly not going to take 24 patches for 3.14 at this point in time. >> What I can do is take all 24 patches into bluetooth-next and let them sit for 1 week and have people test them. And then we go ahead with reverting 3 patches from 3.14. Does that make sense? > Reverting those 3 patches works for me. > -- > Sander >> Regards >> Marcel Hi Marcel, Ping... it seems these 3 reverts are still not in 3.14-rc5 to fix the regressions ? -- Sander -- 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
