Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752804AbbETHLS (ORCPT ); Wed, 20 May 2015 03:11:18 -0400 Received: from lb3-smtp-cloud6.xs4all.net ([194.109.24.31]:44198 "EHLO lb3-smtp-cloud6.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752587AbbETHLQ (ORCPT ); Wed, 20 May 2015 03:11:16 -0400 Message-ID: <1432105871.21715.30.camel@x220> Subject: Re: [PATCH -rfc 4/4] locking/rtmutex: Support spin on owner (osq) From: Paul Bolle To: Davidlohr Bueso Cc: Thomas Gleixner , Peter Zijlstra , Ingo Molnar , Steven Rostedt , Mike Galbraith , "Paul E. McKenney" , Sebastian Andrzej Siewior , linux-kernel@vger.kernel.org, Davidlohr Bueso Date: Wed, 20 May 2015 09:11:11 +0200 In-Reply-To: <1432056298-18738-5-git-send-email-dave@stgolabs.net> References: <1432056298-18738-1-git-send-email-dave@stgolabs.net> <1432056298-18738-5-git-send-email-dave@stgolabs.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 922 Lines: 29 (This is pasted as an RFC, so you probably don't want feedback going into detail yet, but I couldn't help spotting this.) On Tue, 2015-05-19 at 10:24 -0700, Davidlohr Bueso wrote: > --- a/kernel/Kconfig.locks > +++ b/kernel/Kconfig.locks > +config RT_MUTEX_SPIN_ON_OWNER > + def_bool y > + depends on SMP && RT_MUTEXES && !CONFIG_DEBUG_RT_MUTEXES && ARCH_SUPPORTS_ATOMIC_RMW s/CONFIG_DEBUG_RT_MUTEXES/DEBUG_RT_MUTEXES/? Or perhaps even drop "&& !CONFIG_DEBUG_RT_MUTEXES" entirely, because that test currently always evaluates to true, so it might not be needed. Running scripts/checkkconfigsymbols.py --diff $sha1..$sha2 helps catching typos like this. Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/