All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] xfstests: split mapped writes vs direct I/O tests from 091
Date: Thu, 13 Oct 2011 06:06:42 -0500	[thread overview]
Message-ID: <1318504002.3172.28.camel@doink> (raw)
In-Reply-To: <20111010182216.GA1335@infradead.org>

On Mon, 2011-10-10 at 14:22 -0400, Christoph Hellwig wrote:
> This effectively reverts
> 
> 	xfstests: add mapped write fsx operations to 091
> 
> and adds a new test case for it.  It tests something slightly different, and
> regressions in existing tests due to new features are pretty nasty in a
> test suite.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Looks good.  I see no need to re-post just to delete
the "author" line.  Do that as a separate commit that
updates all the tests at once.

Reviewed-by: Alex Elder <aelder@sgi.com>


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2011-10-13 11:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 18:21 [PATCH 1/3] xfstests: fix 122 for recent xfsprogs Christoph Hellwig
2011-10-10 18:22 ` [PATCH 2/2] xfstests: split mapped writes vs direct I/O tests from 091 Christoph Hellwig
2011-10-10 18:22   ` [PATCH 3/3] xfstests: allow 091 for non-xfs filesystems Christoph Hellwig
2011-10-11  2:11     ` Dave Chinner
2011-10-11 12:46       ` Christoph Hellwig
2011-10-11 14:18     ` [PATCH 3/3 v2] " Christoph Hellwig
2011-10-11 22:40       ` Dave Chinner
2011-10-13 11:06       ` Alex Elder
2011-10-11 22:40   ` [PATCH 2/2] xfstests: split mapped writes vs direct I/O tests from 091 Dave Chinner
2011-10-12  7:32     ` Christoph Hellwig
2011-10-13 11:06     ` Alex Elder
2011-10-13 11:06   ` Alex Elder [this message]
2011-10-11 22:36 ` [PATCH 1/3] xfstests: fix 122 for recent xfsprogs Dave Chinner
2011-10-13 11:06 ` Alex Elder

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=1318504002.3172.28.camel@doink \
    --to=aelder@sgi.com \
    --cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.