From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Zhi Yong Wu <zwu.kernel@gmail.com>,
linux-api@vger.kernel.org, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH v2 0/3] xfs: add O_TMPFILE support
Date: Tue, 7 Jan 2014 14:49:38 -0600 [thread overview]
Message-ID: <20140107204938.GE1935@sgi.com> (raw)
In-Reply-To: <20131226085134.GA32660@infradead.org>
Hey Christoph,
On Thu, Dec 26, 2013 at 12:51:34AM -0800, Christoph Hellwig wrote:
> Both patches looks good to me,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> But now we need to make sure we can exercise it, which will need
> support for tmpfile and flink commands in xfs_io.
Are you suggesting that we hold off on this until such time as the tests are
completed?
Thanks,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-07 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 0:22 [PATCH v2 0/3] xfs: add O_TMPFILE support Zhi Yong Wu
2013-12-18 0:22 ` [PATCH v2 1/3] xfs: factor prid related codes into xfs_get_initial_prid() Zhi Yong Wu
2013-12-18 0:22 ` [PATCH v2 2/3] xfs: add O_TMPFILE support Zhi Yong Wu
2013-12-24 0:55 ` Dave Chinner
2013-12-24 1:58 ` Zhi Yong Wu
2013-12-18 0:22 ` [PATCH v2 3/3] xfs: allow linkat() on O_TMPFILE files Zhi Yong Wu
2013-12-24 0:55 ` Dave Chinner
2013-12-23 1:45 ` [PATCH v2 0/3] xfs: add O_TMPFILE support Zhi Yong Wu
2013-12-26 8:51 ` Christoph Hellwig
[not found] ` <20131226085134.GA32660-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-12-28 10:04 ` Zhi Yong Wu
2013-12-28 10:04 ` Zhi Yong Wu
2014-01-07 20:49 ` Ben Myers [this message]
2014-01-07 20:51 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2013-12-18 0:15 Zhi Yong Wu
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=20140107204938.GE1935@sgi.com \
--to=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=xfs@oss.sgi.com \
--cc=zwu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.