From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756031AbcLPR0b (ORCPT ); Fri, 16 Dec 2016 12:26:31 -0500 Received: from mail.fireflyinternet.com ([109.228.58.192]:50422 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755151AbcLPR0W (ORCPT ); Fri, 16 Dec 2016 12:26:22 -0500 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Date: Fri, 16 Dec 2016 17:26:10 +0000 From: Chris Wilson To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, Maarten Lankhorst , Ingo Molnar Subject: Re: [PATCH v2 1/8] locking: Fix compilation of __WW_MUTEX_INITIALIZER Message-ID: <20161216172610.GB29871@nuc-i3427.alporthouse.com> References: <20161201114711.28697-1-chris@chris-wilson.co.uk> <20161201114711.28697-2-chris@chris-wilson.co.uk> <20161216145040.GG3124@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161216145040.GG3124@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 16, 2016 at 03:50:40PM +0100, Peter Zijlstra wrote: > > > Chris, did this series at all depend on the other ww_mutex patches? It is independent. My goal was to try and hit the bugs Nicolai reported. Most of it should be covered by locktorture if we add ww_mutex support to it. -Chris -- Chris Wilson, Intel Open Source Technology Centre