From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Eric Sandeen <sandeen@redhat.com>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH v3] iomap: take responsibility for the filesystem iomap code
Date: Thu, 27 Dec 2018 00:08:40 -0800 [thread overview]
Message-ID: <20181227080840.GB12171@infradead.org> (raw)
In-Reply-To: <20181224003711.GK27208@magnolia>
Looks good:
Acked-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2018-12-27 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 5:36 [RFC PATCH] iomap: take responsibility for the filesystem iomap code Darrick J. Wong
2018-12-20 7:08 ` Christoph Hellwig
2018-12-20 7:27 ` Amir Goldstein
2018-12-20 19:04 ` [PATCH v2] " Darrick J. Wong
2018-12-20 19:07 ` Al Viro
2018-12-21 22:05 ` Dave Chinner
2018-12-24 0:37 ` [PATCH v3] " Darrick J. Wong
2018-12-27 8:08 ` Christoph Hellwig [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=20181227080840.GB12171@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).