From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: david@fromorbit.com, eguan@redhat.com, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: [PATCH 6/9] xfs: fix $XFS_DB_PROG usage
Date: Fri, 30 Sep 2016 04:56:36 -0700 [thread overview]
Message-ID: <20160930115636.GC29955@infradead.org> (raw)
In-Reply-To: <147520222110.26891.18259521392775976412.stgit@birch.djwong.org>
Looks fine,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2016-09-30 11:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 2:23 [PATCH v10 0/9] xfstests: fixes and new tests for rmap/reflink Darrick J. Wong
2016-09-30 2:23 ` [PATCH 1/9] xfs/122: decrease the log update done item sizes Darrick J. Wong
2016-09-30 7:06 ` Christoph Hellwig
2016-09-30 2:23 ` [PATCH 2/9] xfs/130: don't modify files after failed mount Darrick J. Wong
2016-09-30 7:07 ` Christoph Hellwig
2016-09-30 2:23 ` [PATCH 3/9] xfs/{207,327}: fsxattr no longer has the reflink flag Darrick J. Wong
2016-09-30 7:07 ` Christoph Hellwig
2016-09-30 2:23 ` [PATCH 4/9] misc: fix fallocate commands that need the unshare switch Darrick J. Wong
2016-09-30 11:55 ` Christoph Hellwig
2016-09-30 2:23 ` [PATCH 5/9] misc: use get_block_size helper Darrick J. Wong
2016-09-30 11:56 ` Christoph Hellwig
2016-09-30 2:23 ` [PATCH 6/9] xfs: fix $XFS_DB_PROG usage Darrick J. Wong
2016-09-30 11:56 ` Christoph Hellwig [this message]
2016-09-30 2:23 ` [PATCH 7/9] xfs: more rmapbt tests Darrick J. Wong
2016-09-30 2:23 ` [PATCH 8/9] xfs: test realtime rmapbt code Darrick J. Wong
2016-10-07 11:41 ` Eryu Guan
2016-09-30 2:24 ` [PATCH 9/9] xfs: test copy-on-write fragmentation when no cow extent size hint is set Darrick J. Wong
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=20160930115636.GC29955@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).