From: David Howells <dhowells@redhat.com>
To: Eryu Guan <eguan@redhat.com>
Cc: dhowells@redhat.com, Christoph Hellwig <hch@infradead.org>,
mtk.manpages@gmail.com,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: statx manpage
Date: Thu, 09 Mar 2017 06:46:48 +0000 [thread overview]
Message-ID: <21188.1489042008@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170308034500.GY14226@eguan.usersys.redhat.com>
Eryu Guan <eguan@redhat.com> wrote:
> There's a "ADDING TO THE FSQA SUITE" section in README file, basically
> it's telling you to use './new' script to generate new test template. So
> based on what type of new test you're going to create, you could run:
>
> ./new generic # new generic test
> ./new xfs # new xfs test
> ./new ext4 # new ext4 test
> ./new shared # new shared test
> ...
>
> It finds the first free seq number and creates test template and a
> default .out file in tests/<type> dir and add a new entry in
> tests/<type>/group file. You could just edit the template and update
> the .out file with expected output from the test run.
Yes, I'd spotted the ./new script, but it's not as simple as that since shell
scripts can't call system calls directly.
David
next prev parent reply other threads:[~2017-03-09 6:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 0:06 [PATCH] xfs: report crtime and attribute flags to statx Darrick J. Wong
2017-03-07 5:01 ` Christoph Hellwig
2017-03-07 17:23 ` Darrick J. Wong
2017-03-07 17:22 ` statx manpage David Howells
2017-03-07 18:02 ` Darrick J. Wong
2017-03-07 18:39 ` David Howells
2017-03-07 18:44 ` Darrick J. Wong
2017-03-07 18:55 ` David Howells
2017-03-07 21:44 ` Andreas Dilger
2017-03-07 22:55 ` Eric Biggers
2017-03-08 3:45 ` Eryu Guan
2017-03-08 9:24 ` David Howells
2017-03-08 15:26 ` Jeff Layton
2017-03-20 16:01 ` Matthew Wilcox
2017-03-22 10:55 ` Jeff Layton
2017-03-08 9:41 ` David Howells
2017-03-10 5:01 ` Eric Biggers
2017-03-09 6:46 ` David Howells [this message]
2017-03-09 6:59 ` Eryu Guan
2017-03-09 6:59 ` Darrick J. Wong
2017-03-09 14:01 ` Christoph Hellwig
2017-03-09 7:45 ` David Howells
2017-03-24 20:53 ` Eric Biggers
2017-03-27 0:46 ` Andreas Dilger
2017-03-27 15:40 ` Darrick J. Wong
2017-03-27 16:25 ` David Howells
2017-03-27 16:46 ` Christoph Hellwig
2017-03-27 19:04 ` Jeff Layton
2017-03-28 19:39 ` Andreas Dilger
2017-03-28 20:22 ` Jeff Layton
2017-03-31 15:49 ` Christoph Hellwig
2017-03-27 18:57 ` David Howells
2017-03-28 0:13 ` [PATCH] Add initial batch of statx() LTP tests David Howells
2017-03-28 6:28 ` Christoph Hellwig
2017-03-28 8:23 ` David Howells
2017-03-27 9:55 ` statx manpage David Howells
2017-03-31 15:56 ` Christoph Hellwig
2017-03-31 16:43 ` David Howells
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=21188.1489042008@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mtk.manpages@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 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).