From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752765AbbCJMqI (ORCPT ); Tue, 10 Mar 2015 08:46:08 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:60688 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751955AbbCJMqE (ORCPT ); Tue, 10 Mar 2015 08:46:04 -0400 Date: Tue, 10 Mar 2015 13:46:01 +0100 From: Peter Zijlstra To: Sebastian Andrzej Siewior Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Maarten Lankhorst , Mike Galbraith Subject: Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt_mutex instead of mutex for the baselock Message-ID: <20150310124601.GC2896@worktop.programming.kicks-ass.net> References: <1425056229-22326-1-git-send-email-bigeasy@linutronix.de> <1425056229-22326-3-git-send-email-bigeasy@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1425056229-22326-3-git-send-email-bigeasy@linutronix.de> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote: > +static int __sched __mutex_lock_check_stamp(struct rt_mutex *lock, > + struct ww_acquire_ctx *ctx) On that; should we rename this to __ww_mutex_check_wound() ? or something to more clearly reflect what it actually does?