Return-Path: Date: Mon, 3 Mar 2014 20:38:53 +0100 From: Sander Eikelenboom Message-ID: <1335661753.20140303203853@eikelenboom.it> To: Marcel Holtmann CC: Peter Hurley , "Gustavo F. Padovan" , Johan Hedberg , Gianluca Anzolin , Alexander Holler , Andrey Vihrov , "bluez mailin list (linux-bluetooth@vger.kernel.org)" , linux-kernel Subject: Re: [PATCH 00/24] rfcomm fixes In-Reply-To: <1259174563.20140212120644@eikelenboom.it> References: <1391997564-1805-1-git-send-email-peter@hurleysoftware.com> <3E0F3723-029F-4B12-8D77-9790FDBD3227@holtmann.org> <1259174563.20140212120644@eikelenboom.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-ID: 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