From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8901FC07E9A for ; Wed, 14 Jul 2021 09:51:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 686C461358 for ; Wed, 14 Jul 2021 09:51:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238941AbhGNJyI (ORCPT ); Wed, 14 Jul 2021 05:54:08 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:60080 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238271AbhGNJyH (ORCPT ); Wed, 14 Jul 2021 05:54:07 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1626256274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=M5fJRzonGN9uQmme0/djkgIoQ/GhoQQzRXG1HoHzAP8=; b=E8rv9zkmiuP0AMHOg275EmBnnXZvZ3ZBn+s6ygH6fAkrqbA4184R4YXxWpwGjSrwmi9sES TAIE94AuV250j1P2vyfIzejy+yK3oCNJowE2Npf88V7nKB0cmF11mtVmVIsaiXXKfdGUjT Qrmq+vx7zU0BaadfVuHaLP/q6FEiZ0sXuL8+GMfY06wTwCPXbPA5p+ynSVb+1PzeOqKeTc bjufKsHybp8jbar85E4CNUm0onvYFw0oqazB+nrxCfIdRX1FqJxGaLAexqzpDzwKLOY6AF s2Mes51GFvBQyjoAlLkUsXnJbkCGuEPJQHhvyQOWHovw1Ff/rmO13ns0QmOreA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1626256274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=M5fJRzonGN9uQmme0/djkgIoQ/GhoQQzRXG1HoHzAP8=; b=7WfdmIqyGNseiWMY7kVoDy3zQE6mKW4Reso9ZUZocTmhyO62FjebaGu2bw8Qe99OBTW09D PJcwKSt0tzJLmJAg== To: Peter Zijlstra Cc: LKML , Ingo Molnar , Juri Lelli , Steven Rostedt , Daniel Bristot de Oliveira , Will Deacon , Waiman Long , Boqun Feng , Sebastian Andrzej Siewior , Davidlohr Bueso Subject: Re: [patch 16/50] locking/rtmutex: Use rt_mutex_wake_q_head In-Reply-To: <20210714085557.GD2725@worktop.programming.kicks-ass.net> References: <20210713151054.700719949@linutronix.de> <20210713160747.508939354@linutronix.de> <20210714085557.GD2725@worktop.programming.kicks-ass.net> Date: Wed, 14 Jul 2021 11:51:14 +0200 Message-ID: <87v95db4vh.ffs@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 14 2021 at 10:55, Peter Zijlstra wrote: > On Tue, Jul 13, 2021 at 05:11:10PM +0200, Thomas Gleixner wrote: >> + DEFINE_RT_MUTEX_WAKE_Q_HEAD(wqh); >> - DEFINE_WAKE_Q(wake_q); > > The naming doesn't really line up nicely... Would DEFINE_RT_WAKE_Q() > work? Sure.