Return-Path: Message-ID: <55A76D51.6000607@mentor.com> Date: Thu, 16 Jul 2015 09:37:37 +0100 From: Dean Jenkins MIME-Version: 1.0 To: , , Subject: Re: [PATCH v2 3/8] Bluetooth: Unwind l2cap_sock_shutdown() References: <1435078779-4436-1-git-send-email-Dean_Jenkins@mentor.com> <1435078779-4436-4-git-send-email-Dean_Jenkins@mentor.com> <20150713110731.GA21598@t440s.lan> <55A3F5F8.4070800@mentor.com> <20150716080840.GA28234@t440s.lan> In-Reply-To: <20150716080840.GA28234@t440s.lan> Content-Type: text/plain; charset="windows-1252"; format=flowed List-ID: Hi Johan, On 16/07/15 09:08, Johan Hedberg wrote: > Hi Dean, > > On Mon, Jul 13, 2015, Dean Jenkins wrote: >>> Do you think you'll be able to fix this as well as the missing >>> mutex_lock(&conn->chan_lock) issue this week? Otherwise we'll need to >>> consider reverting your patches since it's quite clear we can't make any >>> bluetooth-next pull requests with the current state of the tree. >> I think it would be wise to revert the changes as I am unable to guarantee >> that I get time to propose a fix during this week. I will try to work on a >> v3 patchset based on your feedback. > I went ahead and pushed a rebased tree with your patches 3/8, 4/8 and > 5/8 removed. The other five were either harmless or good fixes. So > if/when you have new patches please base them against the new tree. > > Thanks for the information. I shall endeavour to fix the locking issues but it will take me some days. Regards, Dean -- Dean Jenkins Embedded Software Engineer Linux Transportation Solutions Mentor Embedded Software Division Mentor Graphics (UK) Ltd.