public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: fix 108 and enable it by default
Date: Sun, 12 Sep 2010 23:38:40 -0500	[thread overview]
Message-ID: <4C8DAAD0.9050505@sandeen.net> (raw)
In-Reply-To: <20100912171204.GA7225@infradead.org>

Christoph Hellwig wrote:
> Apply the prjquota check to the scratch device so that it doesn't fail,
> and add the test to the auto and quick groups now that it works.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Ah, after arekm's patch... makes sense.

Reviewed-by: Eric Sandeen <sandeen@sandeen.net>

> Index: xfstests-dev/108
> ===================================================================
> --- xfstests-dev.orig/108	2010-09-12 17:04:58.000000000 +0000
> +++ xfstests-dev/108	2010-09-12 17:05:23.000000000 +0000
> @@ -86,8 +86,8 @@ test_accounting()
>  }
>  
>  export MOUNT_OPTIONS="-opquota"
> -_require_prjquota
>  _qmount
> +_require_prjquota $SCRATCH_DEV
>  
>  # real QA test starts here
>  rm -f $tmp.projects $seq.full
> Index: xfstests-dev/group
> ===================================================================
> --- xfstests-dev.orig/group	2010-09-12 17:05:43.000000000 +0000
> +++ xfstests-dev/group	2010-09-12 17:06:32.000000000 +0000
> @@ -218,7 +218,7 @@ deprecated
>  105 acl auto quick
>  106 quota
>  107 quota
> -108 quota
> +108 quota auto quick
>  109 metadata auto
>  110 repair auto
>  111 ioctl
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

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

      reply	other threads:[~2010-09-13  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 17:12 [PATCH] xfstests: fix 108 and enable it by default Christoph Hellwig
2010-09-13  4:38 ` Eric Sandeen [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=4C8DAAD0.9050505@sandeen.net \
    --to=sandeen@sandeen.net \
    --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