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=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED 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 77547C433FF for ; Thu, 1 Aug 2019 00:22:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 52A382067D for ; Thu, 1 Aug 2019 00:22:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729525AbfHAAWe (ORCPT ); Wed, 31 Jul 2019 20:22:34 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:58532 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726448AbfHAAWe (ORCPT ); Wed, 31 Jul 2019 20:22:34 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: krisman) with ESMTPSA id D7A1B28A8EA From: Gabriel Krisman Bertazi To: Thomas Gleixner Cc: mingo@redhat.com, peterz@infradead.org, dvhart@infradead.org, linux-kernel@vger.kernel.org, kernel@collabora.com Subject: Re: [PATCH RFC 1/2] futex: Split key setup from key queue locking and read References: <20190730220602.28781-1-krisman@collabora.com> <85sgql7nok.fsf@collabora.com> Date: Wed, 31 Jul 2019 20:22:30 -0400 In-Reply-To: <85sgql7nok.fsf@collabora.com> (Gabriel Krisman Bertazi's message of "Wed, 31 Jul 2019 20:07:55 -0400") Message-ID: <85d0hp4tvd.fsf@collabora.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Gabriel Krisman Bertazi writes: > Thomas Gleixner writes: >> What has this to do with futex_requeue()? Absolutely nothing unleass you >> can reused that code there, which I doubt. > >I think it could be reused there Though I admit to not having tried it out. I suppose I can just drop the reference from the commit message when I submit the new version. -- Gabriel Krisman Bertazi