From: Rich Johnston <rjohnston@sgi.com>
To: David Sterba <dsterba@suse.cz>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: enhance ltp/fsx with a timeout option
Date: Wed, 6 Mar 2013 12:31:27 -0600 [thread overview]
Message-ID: <51378B7F.9090103@sgi.com> (raw)
In-Reply-To: <1358944851-14336-1-git-send-email-dsterba@suse.cz>
David,
Thanks for submitting this patch. I like the addition of the -T option.
I used test 263 to verify that fsx works as expected with the new -T and
the existing -N options. With the -T option of course, test 263 will
fail. I don't suggest that we change existing tests but add new tests
which use the new -T option. Do you have a new test which you intend to
use the -T option that can be submitted with this patch?
Thanks
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2013-03-06 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1358944851-14336-1-git-send-email-dsterba@suse.cz>
2013-03-06 18:31 ` Rich Johnston [this message]
2013-03-07 18:25 ` [PATCH] xfstests: enhance ltp/fsx with a timeout option David Sterba
2013-03-07 22:27 ` 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=51378B7F.9090103@sgi.com \
--to=rjohnston@sgi.com \
--cc=dsterba@suse.cz \
--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