public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: fstests@vger.kernel.org
Cc: David Disseldorp <ddiss@suse.de>
Subject: [PATCH 1/2] README: remove incorrect check -udf usage
Date: Mon, 26 Jun 2017 15:40:16 +0200	[thread overview]
Message-ID: <20170626134017.2741-1-ddiss@suse.de> (raw)

The -udf parameter for check does not exist. UDF can still be tested via
the configuration parameter FSTYP=udf.

Signed-off-by: David Disseldorp <ddiss@suse.de>
---
 README | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/README b/README
index fd491e4a..11bf6a94 100644
--- a/README
+++ b/README
@@ -120,12 +120,10 @@ Running tests:
     - Groups of tests maybe ran by: ./check -g [group(s)]
       See the 'group' file for details on groups
     - To randomize test order: ./check -r [test(s)]
-    - You can explicitly specify NFS/CIFS/UDF/OVERLAY, otherwise
+    - You can explicitly specify NFS/CIFS/OVERLAY, otherwise
       the filesystem type will be autodetected from $TEST_DEV:
         - for running nfs tests: ./check -nfs [test(s)]
         - for running cifs/smb3 tests: ./check -cifs [test(s)]
-        - for udf tests: ./check -udf [test(s)]
-          Running all the udf tests: ./check -udf -g udf
         - for overlay tests: ./check -overlay [test(s)]
           The TEST and SCRATCH partitions should be pre-formatted
           with another base fs, where the overlay dirs will be created
-- 
2.12.3


             reply	other threads:[~2017-06-26 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 13:40 David Disseldorp [this message]
2017-06-26 13:40 ` [PATCH 2/2] common: remove tmp.mkfs[err/std] files by name David Disseldorp
2017-06-27  4:33   ` Eryu Guan
2017-06-27  9:55     ` David Disseldorp
2017-06-30  4:18       ` 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=20170626134017.2741-1-ddiss@suse.de \
    --to=ddiss@suse.de \
    --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