From: Rich Johnston <rjohnston@sgi.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests 311: test fsync with dm flakey V3
Date: Fri, 3 May 2013 14:26:12 -0500 [thread overview]
Message-ID: <51840F54.9060206@sgi.com> (raw)
In-Reply-To: <20130503190514.GD12414@localhost.localdomain>
On 05/03/2013 02:05 PM, Josef Bacik wrote:
> On Fri, May 03, 2013 at 12:21:59PM -0600, Rich Johnston wrote:
>> Thanks for another patch Josef, it has been committed with the change
>> discussed.
>>
>
> Err I forgot to point out I already have a "sync" variable in there so it fails
> to compile, we'll need to change the var to do_sync or something. Want me to
> send a patch along? Thanks,
>
> Josef
>
Sorry this was my fault, I have reverted
commit 7f622f44b651aec13b99ef62c2942388a6fbee5d
Author: Rich Johnston <rjohnston@sgi.com>
Date: Fri May 3 14:07:59 2013 -0500
Revert "xfstests 311: test fsync with dm flakey V3"
and committed it again.
commit dd3b5268312e0518ae695e8ee2a618f13805c425
Author: Josef Bacik <jbacik@fusionio.com>
Date: Fri Apr 26 19:13:59 2013 +0000
xfstests 311: test fsync with dm flakey V4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-03 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 19:13 [PATCH] xfstests 311: test fsync with dm flakey V3 Josef Bacik
2013-04-30 7:38 ` Dave Chinner
2013-05-03 12:28 ` Rich Johnston
2013-05-03 17:30 ` Josef Bacik
2013-05-03 18:01 ` Rich Johnston
2013-05-03 18:21 ` Rich Johnston
2013-05-03 19:05 ` Josef Bacik
2013-05-03 19:26 ` Rich Johnston [this message]
2013-05-06 0:19 ` 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=51840F54.9060206@sgi.com \
--to=rjohnston@sgi.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--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