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=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_2 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 95697C352AA for ; Tue, 1 Oct 2019 12:46:55 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 5B5C421872 for ; Tue, 1 Oct 2019 12:46:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lca.pw header.i=@lca.pw header.b="Ip07l89z" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5B5C421872 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lca.pw Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 07ACB8E0005; Tue, 1 Oct 2019 08:46:55 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 029768E0001; Tue, 1 Oct 2019 08:46:54 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E5AA48E0005; Tue, 1 Oct 2019 08:46:54 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0203.hostedemail.com [216.40.44.203]) by kanga.kvack.org (Postfix) with ESMTP id BE3F58E0001 for ; Tue, 1 Oct 2019 08:46:54 -0400 (EDT) Received: from smtpin15.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with SMTP id 64B89181AC9B4 for ; Tue, 1 Oct 2019 12:46:54 +0000 (UTC) X-FDA: 75995190348.15.joke87_2083d74dba1e X-HE-Tag: joke87_2083d74dba1e X-Filterd-Recvd-Size: 4610 Received: from mail-qk1-f194.google.com (mail-qk1-f194.google.com [209.85.222.194]) by imf01.hostedemail.com (Postfix) with ESMTP for ; Tue, 1 Oct 2019 12:46:53 +0000 (UTC) Received: by mail-qk1-f194.google.com with SMTP id x134so11069911qkb.0 for ; Tue, 01 Oct 2019 05:46:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lca.pw; s=google; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=yhYK707SJYezdTmtlm0H5DzhvYDEY+AheUSfJipRwQA=; b=Ip07l89zJ0jmeRNnjuMLfwUjUW/Co9PU7e0m/xjX5PRGmc7z0AHojhkZabJt8X2Bgg g+nON2pSO1jYd3vrOuUPki6rr1yQEu8hEHqD2uxKaL1mXqoQO+mmyIxyk/MqTG+kwh7j k8s6vQHeaqcK2Ex9HxDcxmXOxrevnS6yuu8GEXyqlYjEZ0NonLeaC1CRZJXuD0MLzbKz KMfG1EI87v8Lxz8Ezrm+M3DQJYYjEG8yK9ND3K1qjmeVssoYCQLFRhdCLXQgMe4P5XGr 47iPcjETHnPBpfL8Sd3yLzPtHoVT0IEvJrxtCfa4Pu82gMneNTnjOQOCUx8TaPMdQriE 9BWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=yhYK707SJYezdTmtlm0H5DzhvYDEY+AheUSfJipRwQA=; b=dJFEg30Z0AyNZwf1oBRVrQSIvutAPWcnXGLfTYnozg6kS89NHZc+1oARWhh9HMVmim yFBzlD+hT97c6+CNnZ2xNycjK8nx+jC9vk98RuSiZI4+L5o1e1/I2LDl7uK919i+tJyO 3xSonsUR+beIeayjKHC8Dss8FdX8XiZFl+o/iVHyYNeW/oVSmtHn0BTOAGavFnYeAdCV G9ILXlQHa+BgebgafbCED6goaW8UwyALPT2rVmWPM4SWoe6TwksA8buJ6WVDC+gi1kqy lKktRW+P3VO/T+D3ZInqtYXCXDKa8p4LzE4xULw1BPbI4jCvQJjjCAO3FRhZdZ6GJy5J NsGQ== X-Gm-Message-State: APjAAAVoZEkUqQyrE0ZscjuMpxxdY1jJoIKvW0xezB4dplWVrfCLnZhD AW0cCSpWdk/4jLCmaa8579BcCQ== X-Google-Smtp-Source: APXvYqxfvaAa5fGyRQyIYajobY2F3QEa4iZspmX+Xrdwm3QyJhHVVt0YDLkyzlFTQn8rAQfDdMC0qg== X-Received: by 2002:a37:a9d1:: with SMTP id s200mr5660408qke.251.1569934008434; Tue, 01 Oct 2019 05:46:48 -0700 (PDT) Received: from dhcp-41-57.bos.redhat.com (nat-pool-bos-t.redhat.com. [66.187.233.206]) by smtp.gmail.com with ESMTPSA id n65sm7669877qkb.19.2019.10.01.05.46.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2019 05:46:47 -0700 (PDT) Message-ID: <1569934004.5576.249.camel@lca.pw> Subject: Re: [PATCH -next] treewide: remove unused argument in lock_release() From: Qian Cai To: Peter Zijlstra Cc: akpm@linux-foundation.org, mingo@redhat.com, will@kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, maarten.lankhorst@linux.intel.com, mripard@kernel.org, sean@poorly.run, airlied@linux.ie, daniel@ffwll.ch, dri-devel@lists.freedesktop.org, gregkh@linuxfoundation.org, jslaby@suse.com, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com, intel-gfx@lists.freedesktop.org, tytso@mit.edu, jack@suse.com, linux-ext4@vger.kernel.org, tj@kernel.org, mark@fasheh.com, jlbec@evilplan.org, joseph.qi@linux.alibaba.com, ocfs2-devel@oss.oracle.com, davem@davemloft.net, st@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org, bpf@vger.kernel.org, duyuyang@gmail.com, juri.lelli@redhat.com, vincent.guittot@linaro.org, hannes@cmpxchg.org, mhocko@kernel.org, vdavydov.dev@gmail.com, cgroups@vger.kernel.org, linux-mm@kvack.org, alexander.levin@microsoft.com Date: Tue, 01 Oct 2019 08:46:44 -0400 In-Reply-To: <20190930072938.GK4553@hirez.programming.kicks-ass.net> References: <1568909380-32199-1-git-send-email-cai@lca.pw> <20190930072938.GK4553@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, 2019-09-30 at 09:29 +0200, Peter Zijlstra wrote: > On Thu, Sep 19, 2019 at 12:09:40PM -0400, Qian Cai wrote: > > Since the commit b4adfe8e05f1 ("locking/lockdep: Remove unused argument > > in __lock_release"), @nested is no longer used in lock_release(), so > > remove it from all lock_release() calls and friends. > > Right; I never did this cleanup for not wanting the churn, but as long > as it applies I'll take it. Not sure when you would like to merge this. As you know, the longer it is pending, the more churn it could have. If you could give me rough timeline (i.e., aim for v5.4-rc2 or v5.5), I'll double-check for breakage and rebase it if necessary.