From: Christoph Hellwig <hch@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org, amir73il@gmail.com,
david@fromorbit.com, fstests@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] xfstests: Partially expand the documentation
Date: Fri, 31 Mar 2017 09:27:37 -0700 [thread overview]
Message-ID: <20170331162737.GB1693@infradead.org> (raw)
In-Reply-To: <149097292222.20089.18240501624778225939.stgit@warthog.procyon.org.uk>
Looks fine,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2017-03-31 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 15:08 [PATCH 1/2] xfstests: Add first statx test David Howells
2017-03-31 15:08 ` [PATCH 2/2] xfstests: Partially expand the documentation David Howells
2017-03-31 16:27 ` Christoph Hellwig [this message]
2017-03-31 16:27 ` [PATCH 1/2] xfstests: Add first statx test Christoph Hellwig
2017-03-31 16:48 ` David Howells
2017-03-31 17:19 ` Christoph Hellwig
2017-03-31 17:24 ` David Howells
2017-04-01 7:35 ` Eryu Guan
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=20170331162737.GB1693@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@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).