From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
Steve French <smfrench@gmail.com>,
Ilya Dryomov <idryomov@gmail.com>,
xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Olga Kornievskaia <olga.kornievskaia@gmail.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Dave Chinner <david@fromorbit.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
ceph-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] xfs-linux: copy-file-range-fixes updated to fe0da9c09b2d
Date: Mon, 10 Jun 2019 18:11:32 -0700 [thread overview]
Message-ID: <20190611011132.GP1871505@magnolia> (raw)
In-Reply-To: <CAOQ4uxhkE_TsN7XMBgzxVhEYDw+gZEOOCiZzn9otVwQtB-XHeA@mail.gmail.com>
On Mon, Jun 10, 2019 at 08:14:08PM +0300, Amir Goldstein wrote:
> +CC affected maintainers
>
> On Mon, Jun 10, 2019 at 7:06 PM Darrick J. Wong <darrick.wong@oracle.com> 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?
Yeah, I was going to do that after 24h (i.e. it'll be in Wednesday's
-next) to see if anyone had any last minute "ZOMG this patch has to be
changed" screaming.
> 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.
Noted.
--D
> Thanks,
> Amir.
prev parent reply other threads:[~2019-06-11 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 16:06 [ANNOUNCE] xfs-linux: copy-file-range-fixes updated to fe0da9c09b2d Darrick J. Wong
2019-06-10 17:14 ` Amir Goldstein
2019-06-11 1:11 ` Darrick J. Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190611011132.GP1871505@magnolia \
--to=darrick.wong@oracle.com \
--cc=Anna.Schumaker@netapp.com \
--cc=amir73il@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=idryomov@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=olga.kornievskaia@gmail.com \
--cc=smfrench@gmail.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).