From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] common: add flink support to _require_xfs_io_command
Date: Thu, 13 Mar 2014 22:10:10 +1100 [thread overview]
Message-ID: <20140313111010.GH4263@dastard> (raw)
In-Reply-To: <20140313101433.318632549@bombadil.infradead.org>
On Thu, Mar 13, 2014 at 03:13:03AM -0700, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> common/rc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index 7f9db56..3bd4bcb 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -1318,6 +1318,10 @@ _require_xfs_io_command()
> testio=`$XFS_IO_PROG -F -f -c "pwrite 0 20k" -c "fsync" \
> -c "fiemap -v" $testfile 2>&1`
> ;;
> + "flink" )
> + testio=`$XFS_IO_PROG -T -F -c "flink $testfile" \
> + $TEST_DIR 2>&1`
> + ;;
> *)
> testio=`$XFS_IO_PROG -c "$command help" 2>&1`
> esac
Looks good.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-03-13 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 10:13 [PATCH 0/3] O_TMPFILE tests, v2 Christoph Hellwig
2014-03-13 10:13 ` [PATCH 1/3] common: add flink support to _require_xfs_io_command Christoph Hellwig
2014-03-13 11:10 ` Dave Chinner [this message]
2014-03-13 10:13 ` [PATCH 2/3] generic: add a basic O_TMPFILE test Christoph Hellwig
2014-03-13 11:16 ` Dave Chinner
2014-03-13 10:13 ` [PATCH 3/3] xfs: add a test for unlinked inodes due to O_TMPFILE Christoph Hellwig
2014-03-13 11:29 ` Dave Chinner
2014-04-03 11:07 ` Christoph Hellwig
2014-04-03 21:32 ` Dave Chinner
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=20140313111010.GH4263@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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