Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755606AbcKKLi5 (ORCPT ); Fri, 11 Nov 2016 06:38:57 -0500 Received: from merlin.infradead.org ([205.233.59.134]:56916 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752395AbcKKLi4 (ORCPT ); Fri, 11 Nov 2016 06:38:56 -0500 Date: Fri, 11 Nov 2016 12:38:10 +0100 From: Peter Zijlstra To: Daniel Vetter Cc: Linus Torvalds , Waiman Long , Jason Low , Ding Tianhong , Thomas Gleixner , Will Deacon , Ingo Molnar , Imre Deak , Linux Kernel Mailing List , Davidlohr Bueso , Tim Chen , Terry Rudd , "Paul E. McKenney" , Jason Low , Chris Wilson , Rob Clark Subject: Re: [PATCH -v4 1/8] locking/drm: Kill mutex trickery Message-ID: <20161111113810.GF3117@twins.programming.kicks-ass.net> References: <20161007145243.361481786@infradead.org> <20161007150210.927453282@infradead.org> <20161018124841.GW3117@twins.programming.kicks-ass.net> <20161018125718.GG3157@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 420 Lines: 10 On Fri, Nov 11, 2016 at 12:22:02PM +0100, Daniel Vetter wrote: > Once all your locking rework is assembled it might be good to have a > topic branch I could pull in. Both for testing and to handle conflicts > before it goes boom in the merge window ;-) Not necessary ofc, but I > think it'd be useful. Everything except the trylock_recursive is already in tip/locking/core. Ingo, is that all there is in that branch?