All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: fstests@vger.kernel.org
Cc: Eryu Guan <eguan@redhat.com>
Subject: [PATCH 2/2] xfs/287: fix wrong seq number in test
Date: Wed, 28 Sep 2016 11:44:10 +0800	[thread overview]
Message-ID: <1475034250-6909-2-git-send-email-eguan@redhat.com> (raw)
In-Reply-To: <1475034250-6909-1-git-send-email-eguan@redhat.com>

It's 287 not 285.

Signed-off-by: Eryu Guan <eguan@redhat.com>
---
 tests/xfs/287 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/xfs/287 b/tests/xfs/287
index aca410a..766c91e 100755
--- a/tests/xfs/287
+++ b/tests/xfs/287
@@ -1,5 +1,5 @@
 #! /bin/bash
-# FS QA Test No. 285
+# FS QA Test No. 287
 #
 # Test to verify project quota xfs_admin, xfsdump/xfsrestore and
 # xfs_db functionality
-- 
2.7.4


  reply	other threads:[~2016-09-28  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28  3:44 [PATCH 1/2] generic/052: use _check_scratch_fs not _xfs_check Eryu Guan
2016-09-28  3:44 ` Eryu Guan [this message]
2016-09-29  6:29   ` [PATCH 2/2] xfs/287: fix wrong seq number in test Dave Chinner
2016-09-29  6:28 ` [PATCH 1/2] generic/052: use _check_scratch_fs not _xfs_check Dave Chinner
2016-09-29  8:01 ` Zorro Lang

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=1475034250-6909-2-git-send-email-eguan@redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    /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.