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=-7.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 7C283C07E96 for ; Tue, 13 Jul 2021 20:24:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6388461360 for ; Tue, 13 Jul 2021 20:24:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235251AbhGMU07 (ORCPT ); Tue, 13 Jul 2021 16:26:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231499AbhGMU06 (ORCPT ); Tue, 13 Jul 2021 16:26:58 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D1DF5C0613DD; Tue, 13 Jul 2021 13:24:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Content-Transfer-Encoding: Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To: Subject:Sender:Reply-To:Content-ID:Content-Description; bh=5/KBP87pxftrobVJwcPVKbF/bN/LJFwKGUBAPeXS5hE=; b=DEhXLD6vRlQBOF1tVBA1ZlR1iY G5R9qtBjFVqD1l4yAewXP7lIB5wFcu2WWkjBcnURj7K/GCaa0WlAw7bqLmyNjZtaPqdcmwa2AXeuu OZh7l74BpwEif50/Pa0tMKza/WnalkWjCOjNDuEDNx75MOn1Q8slglyIHOJ8KVppTlEJsaTZhpdFV KDf9zx4IURkiuHeEtWio1s6wxGzTjhl940lXWkGiPNGpu+N6ttX3wd+rQ1bss1r6YhTxebX8LQ5To 3jeTWUZtseI98aptkk/DtnmIG9DvIljdXDhCHRiYszSRCJgNktQqd38x5ZNjEs/pMUx+Yd7iJiaNV GRYprOdA==; Received: from [2601:1c0:6280:3f0::aefb] by bombadil.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1m3Owp-00BIzD-8p; Tue, 13 Jul 2021 20:24:07 +0000 Subject: Re: [GIT PULL] vboxsf fixes for 5.14-1 To: Al Viro , Linus Torvalds Cc: Hans de Goede , linux-fsdevel , LKML References: <30c7ec73-4ad5-3c4e-4745-061eb22f2c8a@redhat.com> From: Randy Dunlap Message-ID: Date: Tue, 13 Jul 2021 13:24:06 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/13/21 1:18 PM, Al Viro wrote: > On Tue, Jul 13, 2021 at 08:14:04PM +0000, Al Viro wrote: >> On Tue, Jul 13, 2021 at 12:15:13PM -0700, Linus Torvalds wrote: >>> On Tue, Jul 13, 2021 at 3:45 AM Hans de Goede wrote: >>>> ... >>> >>> (When something then touches the *common* vfs code, that's a different >>> thing - but something like this vboxsf thing this pull request looks >>> normal to me). >> >> To elaborate a bit - there's one case when I want it to go through >> vfs.git, and that's when there's an interference between something >> going on in vfs.git and the work done in filesystem. > > Example: if there's a series changing calling conventions for some method > brewing in vfs.git and changes to filesystem's instance of that method > in the filesystem tree. Then I'd rather it coordinated before either > gets merged. It might be an invariant branch in either tree pulled by > both, it might be a straight pull into vfs.git and sorting the things out > there - depends upon the situation. > Hi Al, Where would you prefer for kernel-doc changes in fs/*.[ch] be merged? E.g., from June 27: https://lore.kernel.org/linux-fsdevel/20210628014613.11296-1-rdunlap@infradead.org/ thanks. -- ~Randy