From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-xfs@vger.kernel.org, Jan Kara <jack@suse.cz>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 4/4] ext4: Switch to iomap for SEEK_HOLE / SEEK_DATA
Date: Mon, 18 Sep 2017 11:59:37 -0700 [thread overview]
Message-ID: <20170918185937.GO6540@magnolia> (raw)
In-Reply-To: <CAHc6FU6X29Pr6gA+d0L3WuoCY1XwNjQ9aTYUuAp84-O-ff_xGQ@mail.gmail.com>
On Mon, Sep 18, 2017 at 07:52:32PM +0200, Andreas Gruenbacher wrote:
> On Thu, Sep 14, 2017 at 11:15 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> > On Thu, Sep 14, 2017 at 04:06:19PM +0200, Andreas Gruenbacher wrote:
> >> From: Christoph Hellwig <hch@lst.de>
> >>
> >> Here we go, after another round of xfstests.
> >>
> >> The next question, since it touches vfs infrastructure, is which tree
> >> this patch queue should be merged through. Al?
> >
> > Discussions with Darrick before he went on vacation/honeymoon was that
> > up until now changes to fs/iomap.c had been going through XFS, but
> > since these changes didn't affect XFS, and the rest of the patch
> > series touches ext4 and ext4 functionality, that he was OK with
> > running this patch series through the ext4 tree.
>
> That sure works for me.
Me too.
(Back from vacation, weeding his way through 2400 emails...)
--D
>
> Andreas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-09-18 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 14:06 [PATCH v3 4/4] ext4: Switch to iomap for SEEK_HOLE / SEEK_DATA Andreas Gruenbacher
2017-09-14 21:15 ` Theodore Ts'o
2017-09-18 17:52 ` Andreas Gruenbacher
2017-09-18 18:59 ` 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=20170918185937.GO6540@magnolia \
--to=darrick.wong@oracle.com \
--cc=agruenba@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).