Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752490AbcCVVqn (ORCPT ); Tue, 22 Mar 2016 17:46:43 -0400 Received: from e06smtp12.uk.ibm.com ([195.75.94.108]:52030 "EHLO e06smtp12.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751352AbcCVVqk (ORCPT ); Tue, 22 Mar 2016 17:46:40 -0400 X-IBM-Helo: d06dlp03.portsmouth.uk.ibm.com X-IBM-MailFrom: heiko.carstens@de.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Tue, 22 Mar 2016 22:46:28 +0100 From: Heiko Carstens To: Peter Zijlstra Cc: Davidlohr Bueso , tglx@linutronix.de, mingo@kernel.org, bigeasy@linutronix.de, umgwanakikbuti@gmail.com, paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, kmo@daterainc.com Subject: Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Message-ID: <20160322214628.GA3528@osiris> References: <20160308220539.GB4404@linux-uzut.site> <20160314134038.GZ6356@twins.programming.kicks-ass.net> <20160321181622.GB32012@linux-uzut.site> <20160322102153.GL6344@twins.programming.kicks-ass.net> <20160322113221.GA3921@osiris> <20160322122050.GM6344@twins.programming.kicks-ass.net> <20160322132600.GC3921@osiris> <20160322135530.GR6344@twins.programming.kicks-ass.net> <20160322144537.GE3921@osiris> <20160322164122.GS6344@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160322164122.GS6344@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16032221-0009-0000-0000-00000AA20E12 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1051 Lines: 28 On Tue, Mar 22, 2016 at 05:41:22PM +0100, Peter Zijlstra wrote: > On Tue, Mar 22, 2016 at 03:45:37PM +0100, Heiko Carstens wrote: > > > Sure, looks nice and makes a lot of sense. And the text looks a bit familiar > > to me ;) > > > > Could you provide From: and Signed-off-by: lines? > > Of course, find below. > > --- > Subject: s390: Clarify pagefault interrupt > From: Peter Zijlstra > > While looking at set_task_state() users I stumbled over the s390 pfault > interrupt code. Since Heiko provided a great explanation on how it > worked, I figured we ought to preserve this. > > Also make a few little tweaks to the code to aid in readability and > explicitly comment the unusual blocking scheme. > > Based-on-text-by: Heiko Carstens > Signed-off-by: Peter Zijlstra (Intel) > --- > arch/s390/mm/fault.c | 44 ++++++++++++++++++++++++++++++++++++-------- > 1 file changed, 36 insertions(+), 8 deletions(-) Applied, with some whitespace changes from me. Thank you!