From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: filter projid32bit info out of growfs & info output
Date: Tue, 15 Oct 2013 12:16:42 -0700 [thread overview]
Message-ID: <20131015191642.GB3008@infradead.org> (raw)
In-Reply-To: <20131008004317.GR4446@dastard>
On Tue, Oct 08, 2013 at 11:43:17AM +1100, Dave Chinner wrote:
> Yup, that's needed. There's a bunch of other things we need to do to
> correctly test 16/32bit project ids without failures. Have a look
> here:
>
> http://oss.sgi.com/archives/xfs/2013-06/msg00219.html
>
> For the mods I posted back in June to avoid failures with the CRC
> enabled filesystems in tests that assume certain options can be
> turned on/off on XFS filesystems.
>
> I'm still running xfstests with that patch....
Would be good to get it in ASAP!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-10-15 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 20:09 [PATCH] xfstests: filter projid32bit info out of growfs & info output Eric Sandeen
2013-10-08 0:43 ` Dave Chinner
2013-10-15 19:16 ` Christoph Hellwig [this message]
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=20131015191642.GB3008@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=sandeen@redhat.com \
--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