From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:57014 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726273AbeKBHKP (ORCPT ); Fri, 2 Nov 2018 03:10:15 -0400 Date: Thu, 1 Nov 2018 22:05:19 +0000 From: Al Viro To: Linus Torvalds Cc: dhowells@redhat.com, swhiteho@redhat.com, john.johansen@canonical.com, alan.christopher.jenkins@gmail.com, ebiederm@redhat.com, linux-fsdevel@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [git pull] mount API series Message-ID: <20181101220518.GT32577@ZenIV.linux.org.uk> References: <20181031053355.GQ32577@ZenIV.linux.org.uk> <28156.1541092687@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Nov 01, 2018 at 11:33:31AM -0700, Linus Torvalds wrote: > Al - can I ask you to look at helping David with something like that? > You tend to be very good at generating those patch-series with > "obviously no changes" for the individual patches, but the end result > ends up being totally different from the starting point (I'm thinking > of all the locking and dentry refcounting series). I'll try. Before we go there, I'd like to get the rest of vfs.git off my hands - AFS series and misc pile. Will send pull requests shortly, then - this stuff. Do you mind if we end up with work.mount rebased? The usual objections re testing in -next do not apply in this case, AFAICS...