From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH] xfs: don't allow DAX on reflink filesystems
Date: Fri, 2 Feb 2018 01:51:31 -0800 [thread overview]
Message-ID: <20180202095131.GB17952@infradead.org> (raw)
In-Reply-To: <20180131222324.GH4849@magnolia>
On Wed, Jan 31, 2018 at 02:23:24PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Now that reflink is no longer experimental, reject attempts to mount
> with DAX until that whole mess gets sorted out.
Didn't I send exactly the same patch about a week ago?
next prev parent reply other threads:[~2018-02-02 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 22:23 [PATCH] xfs: don't allow DAX on reflink filesystems Darrick J. Wong
2018-01-31 23:11 ` Bill O'Donnell
2018-01-31 23:17 ` Bill O'Donnell
2018-01-31 23:52 ` Dave Chinner
2018-02-02 9:51 ` Christoph Hellwig [this message]
2018-02-02 17:47 ` Darrick J. Wong
2018-02-02 18:08 ` Christoph Hellwig
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=20180202095131.GB17952@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--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).