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=-5.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,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 C5C46C31E40 for ; Mon, 10 Jun 2019 17:14:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9EAF2207E0 for ; Mon, 10 Jun 2019 17:14:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tXKr1ajX" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387492AbfFJROV (ORCPT ); Mon, 10 Jun 2019 13:14:21 -0400 Received: from mail-yw1-f68.google.com ([209.85.161.68]:35366 "EHLO mail-yw1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387456AbfFJROU (ORCPT ); Mon, 10 Jun 2019 13:14:20 -0400 Received: by mail-yw1-f68.google.com with SMTP id k128so4079597ywf.2; Mon, 10 Jun 2019 10:14:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kZcaNkyUCHyNNBHCoFIDrPq60f5nJL8w+ttSw5Z4HYU=; b=tXKr1ajXOv3jcM26Ep7l86d6gJSnAXkSrsCwbr7KQPUfrYbaTxEHsAIBRAokJLhpyM qBCrLvuXnUIbm40qjv3fJG0yOnYQoDqCW4OCC6NynBHBZ5QZ3cQElHVb5Zychgt36kBl 88w5NO3d/KU8YUZWQAQXVzabVW+m+9yPHmrWOaOV0dm6+FN5fGd3NUK0V0CqB7iG5/5y o9YN2ka6v/1Ot4PbM8kngQDDhPrTKMDl7bWWD1Ic1/TePG5cJciif3qeaUuaipfWLpVm MtPnP08UW4YmraTfMaYAPf6mJ0+S4uMGkm7Ed7BkVa6URZcIwl3lVOWkEmugGjT2AP9j lGLw== 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=kZcaNkyUCHyNNBHCoFIDrPq60f5nJL8w+ttSw5Z4HYU=; b=jCze4pHqo+/agVWX6uC/UBFJU/vclrk9ZEWXqmLlSVKa9zimfdoO9KLpd5xtnnyBUd azksL7XbHKmS3v+gqvn1Ujwni4pp9S6LJqVwim9HQodY2b5qvak4jl9rQkwBuyA80PY6 dslaKmt7tWNVXS4eOkCvnn7mfJiEgEKXGQ4OaWQW6tptA7IAsJp0pfMd5yAEtDcY4caw ETY02mg5dGg4EfW/oEyaLWr3DjWrOsC2tDvc6TKECYl2iNt4RpSS4IuCoSvlmltYbkb+ bqE4x8/67MY9EupYjZZjCmMWW8kUmOWAYRwVvxsZyT2hiww06Bxe13EUYx6Qlpok0nAh l4HA== X-Gm-Message-State: APjAAAVcTwGOPjFibPnsBBgHGrvSgU267/KIKGX/70pOMgH1jrgIALZW LpnAcWwsOcDAb8XwysH3rglf5ZAIJcvhk0xQPfQ= X-Google-Smtp-Source: APXvYqylMkXtCRaqRsONVov9vQReTdASSa/0yVxjCKKAD/fKBdISmUPR06X1sfw/WpWVbF/sEM/mSKgtSHDke8IPELg= X-Received: by 2002:a81:374c:: with SMTP id e73mr27985620ywa.379.1560186859913; Mon, 10 Jun 2019 10:14:19 -0700 (PDT) MIME-Version: 1.0 References: <20190610160624.GG1871505@magnolia> In-Reply-To: <20190610160624.GG1871505@magnolia> From: Amir Goldstein Date: Mon, 10 Jun 2019 20:14:08 +0300 Message-ID: Subject: Re: [ANNOUNCE] xfs-linux: copy-file-range-fixes updated to fe0da9c09b2d To: "Darrick J. Wong" , Miklos Szeredi , Anna Schumaker , Steve French , Ilya Dryomov Cc: xfs , linux-fsdevel , Olga Kornievskaia , "Theodore Ts'o" , Dave Chinner , Linux NFS Mailing List , CIFS , ceph-devel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org +CC affected maintainers On Mon, Jun 10, 2019 at 7:06 PM Darrick J. Wong wrote: > > Hi folks, > > The copy-file-range-fixes branch of the xfs-linux repository at: > > git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git > > has just been updated. This is a common branch from which everyone else > can create their own copy-file-range fix branches for 5.3. When you > send your pull request to Linus please let him know that the fixes > stream out from here like some kind of hydra. :) Thanks Darrick! Should we also request to include this branch in linux-next? Attention nfs/cifs/fuse/ceph maintainers! This branch includes changes to your filesystems. At lease nfs/cifs/ceph have been tested with these changes and the new xfstests. I think it would be preferred if you merge Darrick's branch into your 5.3 branch as soon as you have one ready to reduce chances of conflicts down the road. I will be sending out 2 more patches to cifs/ceph, which depend on this branch directly to maintainers. Thanks, Amir.