From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfstests: fix 122 for recent xfsprogs
Date: Wed, 12 Oct 2011 09:36:54 +1100 [thread overview]
Message-ID: <20111011223654.GF3159@dastard> (raw)
In-Reply-To: <20111010182156.GA1323@infradead.org>
On Mon, Oct 10, 2011 at 02:21:56PM -0400, Christoph Hellwig wrote:
> - filter out xfs_alloctype_t, this was an internal emum that got removed
> - filter out xfs_bmbt_rec_32_t, this is a variant of the xfs_bmbt_rec_t
> that had almost no users and was removed
> - filter out xfs_dinode_core_t, the separate dinode core is gone, and just
> checking the size of the full dinode is enough
> - accept xfs_bmbt_rec_t as the new canonical name for xfs_bmbt_rec_64_t,
> and replace the old name with the new one in the output stream.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-11 22:36 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
2011-10-11 22:36 ` Dave Chinner [this message]
2011-10-13 11:06 ` [PATCH 1/3] xfstests: fix 122 for recent xfsprogs 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=20111011223654.GF3159@dastard \
--to=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox