public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs/259: disable CRC if testing with 512 bytes block size
Date: Sat, 5 Mar 2016 12:45:17 -0800	[thread overview]
Message-ID: <20160305204517.GA10065@infradead.org> (raw)
In-Reply-To: <1456937518-20505-1-git-send-email-eguan@redhat.com>

This will force crcs off for all the blocksizes.  We should
either always skip 512 bytes, or disable crcs only for the 512 byte
inode size case.  The first seems either, but the second would give
better test coverage.

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

  reply	other threads:[~2016-03-05 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 16:51 [PATCH] xfs/259: disable CRC if testing with 512 bytes block size Eryu Guan
2016-03-05 20:45 ` Christoph Hellwig [this message]
2016-03-07  3:04   ` Eryu Guan

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=20160305204517.GA10065@infradead.org \
    --to=hch@infradead.org \
    --cc=eguan@redhat.com \
    --cc=fstests@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