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=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS autolearn=ham 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 94BFBC10F11 for ; Mon, 22 Apr 2019 21:57:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5833E2064A for ; Mon, 22 Apr 2019 21:57:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1555970238; bh=dY1Su9dQmYiUkU6AHwXA6nOYPbk1wnTltNut4Yp7R+E=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=h+LJvxWHANEhBAHmQfWQoP8npAuqGS4fLjZMphfAWuCMOrLXgkpkWNsAw9+y4GIPY 9B8mRbAVi8nUZeuCcPqFQuiXfJ1gazqcjIVKU1fOv6/6gReFtw9DNxpCLeHravYsGz VszfYJ0Cl2CCVhSqgUbhDFRnrjEDnOyQttsIHRrA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728679AbfDVV5R (ORCPT ); Mon, 22 Apr 2019 17:57:17 -0400 Received: from mail-lf1-f65.google.com ([209.85.167.65]:33666 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727670AbfDVV5R (ORCPT ); Mon, 22 Apr 2019 17:57:17 -0400 Received: by mail-lf1-f65.google.com with SMTP id j11so10080715lfm.0 for ; Mon, 22 Apr 2019 14:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4YlKYa3TQ1kuoOrxS+gPcL63NFPtXMSxMgiFITTKoOg=; b=ETNwPb1rfyoao4c9RzXoOH/cx7pgjLwiwAP5qP1C5hzfEX18s5fW1edRr41PQbWByx KzhtCB8ORq7GgFu1cr+C0FbEhbN4dR763atOiLl/2RTj0FWO5cDrXbm4NP4dq/ZRVKak eArbmgAeiN+Y/Cz+HP5NM8L6L1O3Excecq3cM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4YlKYa3TQ1kuoOrxS+gPcL63NFPtXMSxMgiFITTKoOg=; b=MDiWWnHyuvsFyve5k1PnmvMw9YNeNi0t1oIedcLrUDO2cgM/ME1fgod3LAWVEMtElY gZEiIlxFfx+MY59uIo1Qx2Yu2ShB3izYxcevQeNKAJ2sxerWkQ07Byiv7+xtp6vXHFRN 7p8axZUjk1rGczqh5PczF4OcDfXi78BgHmpFZ1iSWGe4qgkEs5ipQyeTk4Cd7g/3nO3V dYfpZQ8XlGCpeSyR7fIqMqlOYbpjA89DYXXMzLLAUM0JAfQLCuJA51FGyhA3wWCIFG65 0blyShtEb4peUjxv7YTcqUnFIeBMQSD3m62hw4kKe/KfejxkPQ256zy4V/lH1q09Nti5 wq+Q== X-Gm-Message-State: APjAAAV4I/2cg28/+O8QFl43M+QIKWPHOIfzTdfydLKy8igQyNm3stFU Z2KcmD/SVWlr4W5penAneO3yeYct494= X-Google-Smtp-Source: APXvYqyDJbq5U32tLaJ1zpKrR/SayCiNUSN9WpVQfNycgdx1a4qdy5Iw1fzzADnINXwbKm7chbq8xQ== X-Received: by 2002:a19:f50e:: with SMTP id j14mr10571290lfb.11.1555970234748; Mon, 22 Apr 2019 14:57:14 -0700 (PDT) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com. [209.85.167.45]) by smtp.gmail.com with ESMTPSA id g79sm2954915lje.25.2019.04.22.14.57.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Apr 2019 14:57:13 -0700 (PDT) Received: by mail-lf1-f45.google.com with SMTP id a28so10054158lfo.7 for ; Mon, 22 Apr 2019 14:57:13 -0700 (PDT) X-Received: by 2002:a19:ca02:: with SMTP id a2mr11388505lfg.88.1555970233102; Mon, 22 Apr 2019 14:57:13 -0700 (PDT) MIME-Version: 1.0 References: <20190416174900.GT2217@ZenIV.linux.org.uk> <20190416175340.21068-1-viro@ZenIV.linux.org.uk> <20190416175340.21068-60-viro@ZenIV.linux.org.uk> In-Reply-To: From: Linus Torvalds Date: Mon, 22 Apr 2019 14:56:57 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC PATCH 60/62] orangefs: make use of ->free_inode() To: Mike Marshall Cc: Al Viro , Martin Brandenburg , LKML , linux-fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, Apr 22, 2019 at 2:14 PM Mike Marshall wrote: > > I applied your "new inode method: ->free_inode()" and > "orangefs: make use of ->free_inode()" to our pagecache > branch (I hope to get it pulled in the next merge window). Actually, please don't. Exactly because this needs that common vfs patch, I'd really prefer to get it all through Al's tree, rather than have individual filesystems apply their own copies of the common infrastructure commit, and then apply their changes on top of that. I can easily handle any trivial conflicts this causes, so that's not a reason to have each filesystem do it either. So if this is at the top of your tree, can you just "git reset" it away and I'll get all the filesystems (and the common infrastructure commit) all together from Al. Linus