From: Eryu Guan <eguan@redhat.com>
To: fstests@vger.kernel.org
Cc: fdmanana@kernel.org, Eryu Guan <eguan@redhat.com>
Subject: [PATCH] generic/422: check fallocate KEEP_SIZE flag correctly
Date: Mon, 10 Apr 2017 11:18:28 +0800 [thread overview]
Message-ID: <20170410031828.2110-1-eguan@redhat.com> (raw)
"-k" should be passed to _require_xfs_io_command() as a separate
parameter.
Signed-off-by: Eryu Guan <eguan@redhat.com>
---
Hi Filipe,
This is a merge error, I did correct updates to _require_xfs_io_command() and
generic/071 but forgot generic/422. Sorry again for the whole mess :-(
(Not sure why my release testing didn't catch this merge error, I guess it had
something to do with post-release-testing modifications to the stage tree when
I dropped statx tests)
tests/generic/422 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/generic/422 b/tests/generic/422
index cae76a9..a42a30d 100755
--- a/tests/generic/422
+++ b/tests/generic/422
@@ -48,7 +48,7 @@ _supported_fs generic
_supported_os Linux
_require_test
_require_scratch
-_require_xfs_io_command "falloc -k"
+_require_xfs_io_command "falloc" "-k"
_require_odirect
rm -f $seqres.full
--
2.9.3
reply other threads:[~2017-04-10 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170410031828.2110-1-eguan@redhat.com \
--to=eguan@redhat.com \
--cc=fdmanana@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox