Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp833040imm; Fri, 22 Jun 2018 06:08:06 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKmxNjr2GObs9zaLbGLtHNTAL33DMm0cQOnCJjpHAfdq1DV6P3kdljfhoGljE6OJZPPgmTS X-Received: by 2002:a62:a0c:: with SMTP id s12-v6mr1705106pfi.33.1529672886262; Fri, 22 Jun 2018 06:08:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529672886; cv=none; d=google.com; s=arc-20160816; b=RGKCqPhPCoBzeLAF6q1BSwDI7WPKe9gZjSbfbOwy7xA5xhYdfyrGQ9HOWbM0lWPkOv 2G9tcd0is0cLyAE5tg/4eO/rNO4KUXhhNTcDcez+g9Yu5DH3HUk2yXBTKxdB5nbAtX4k SFlmwdeVOFvx6RB2VWRYuBq3lKCuHE0cUhBrHqSbqp8Iu5dHTel0RsFLim76KFwjugnn t30GRq+B5CiSicQtffXzjRhBSl0H3U1+vu+lukK1hexVk9Bk69fa/O08mRyM9Fz8BT43 I/EjmpoxE/4tfhIdUaGhNa9/bZ6Rs8ErVcG9Dpe2/G73BZg+gW5JuIw8wCjjYsiQH5gc AfbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=3fmeKyhw0MRgtCmbP4bKgdhDlUGhWK8qhY16i1f0tsg=; b=BgQeDUrYOpopWdCHUoJxc9Qwx6X8RA1UwA9g4un4hA+qBa1ZTvbM57aX1AuqVkBw/j eRIk++0WmsgcxQWJnxHd2LWPC7+1RTxzX9xPCIR80zRWRP8maRUGKd7FwZptxSQ2GLuB jRi8FSoAYUz6m3/Oxik+H/Q4sMxtf5wm8jk5wx3aoNeWuA/aDkZ3wMJCqz3C6vfNmqV4 nCP9adk02qn63NOTzG+F7W8iyQFZ7Asmj0aNNncXURYdTMNnsVSpUY8MKxx0IHwXV+8V 5sI2wS7oNBcdhDBV5NK88EDzaOaOVJWJtuCzUanSwcHv+IFFaPFlpIjtGQoWSMqYyGPq v1SQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x1-v6si7325823plb.8.2018.06.22.06.07.51; Fri, 22 Jun 2018 06:08:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753277AbeFVNG0 (ORCPT + 99 others); Fri, 22 Jun 2018 09:06:26 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:33768 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750853AbeFVNGY (ORCPT ); Fri, 22 Jun 2018 09:06:24 -0400 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.87 #1 (Red Hat Linux)) id 1fWLlJ-0000R6-1z; Fri, 22 Jun 2018 13:06:01 +0000 Date: Fri, 22 Jun 2018 14:06:01 +0100 From: Al Viro To: David Howells Cc: Reinette Chatre , Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: manual merge of the tip tree with the vfs tree Message-ID: <20180622130600.GY30522@ZenIV.linux.org.uk> References: <20180622115346.1e9cc433@canb.auug.org.au> <29411.1529671523@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29411.1529671523@warthog.procyon.org.uk> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 22, 2018 at 01:45:23PM +0100, David Howells wrote: > Reinette Chatre wrote: > > > Thomas and David, please let me know what I can do from my side to help > > with this. > > You could try basing on Al Viro's for-next tree which has the mount API > changes in it. Umm... That would be a massive headache for everyone involved; the changes in there have very little in common with what you are doing in rdt_mount(), so it might make sense to start with a minimal never-rebased branch that would * define rdt_pseudo_lock_init as 0 * define rdt_pseudo_lock_release as empty * do the rdt_mount() part of a3dbd01e6c9d * have commit message along the lines of "hooks in rdt_mount() for rdt_pseudo_lock to use Functionally a no-op right now; the only reason for having that as a never-rebased branch to get rdt_pseudo_lock and mount series out of each other's hair" Base that on -rc1, then pull it into your rdt branch and David could pull the same into his.