From: Rich Johnston <rjohnston@sgi.com>
To: Jan Schmidt <list.xfs@jan-o-sch.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: add execution of a custom command to fsstress (-x and -X options)
Date: Thu, 9 May 2013 14:47:34 -0500 [thread overview]
Message-ID: <518BFD56.9080605@sgi.com> (raw)
In-Reply-To: <5183CCFB.8060505@jan-o-sch.net>
On 05/03/2013 09:43 AM, Jan Schmidt wrote:
>
> Looks like there are no suggestions how to make -x useful for multiple workers.
> Can we then have the single worker solution (original patch) merged for now?
>
> -Jan
I don't see why not. Looks good.
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-09 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 10:59 [PATCH] xfstests: add execution of a custom command to fsstress (-x and -X options) Jan Schmidt
2013-03-21 19:50 ` Dave Chinner
2013-03-21 20:51 ` Jan Schmidt
2013-03-21 21:12 ` Dave Chinner
2013-03-22 7:06 ` Jan Schmidt
2013-03-24 23:51 ` Dave Chinner
2013-04-05 12:07 ` Jan Schmidt
2013-05-03 14:43 ` Jan Schmidt
2013-05-09 19:47 ` Rich Johnston [this message]
2013-05-09 19:50 ` Rich Johnston
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=518BFD56.9080605@sgi.com \
--to=rjohnston@sgi.com \
--cc=list.xfs@jan-o-sch.net \
--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