From: Jan Kara <jack@suse.cz>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: [PATCH 0/3 v2] Output selection
Date: Tue, 24 Nov 2015 11:39:55 +0100 [thread overview]
Message-ID: <1448361598-28438-1-git-send-email-jack@suse.cz> (raw)
From: Jan Kara <jack@suse.com>
Hello,
the patch series below addresses some issues with test ext4/001. First two
patches improve _link_out_file helper function to allow selection of output
(or in general linking any file when using _link_out_file_named() variant)
based on a feature string (usually mount options, fs features, operating
system) passed to the function (if no feature string is passed, the function
defaults to using "operating system name","mount options"). This feature
is useful when e.g. different mount options change behavior of the filesystem
and thus different output is generated but we want to have the test working
for all mount options.
Patch 3 uses the output selection function in ext4/001 to select different
output files based on mount options.
Comments welcome!
Honza
--
Changes since v1:
* rebased on the current head of xfstests
* integrated output selection with _link_out_file and converted all tests
using it
next reply other threads:[~2015-11-24 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 10:39 Jan Kara [this message]
2015-11-24 10:39 ` [PATCH 1/3] common: Factor out function to get OS name Jan Kara
2015-12-07 23:24 ` Theodore Ts'o
2015-11-24 10:39 ` [PATCH 2/3] common: Improve _link_output_file to be more versatile Jan Kara
2015-12-07 23:26 ` Theodore Ts'o
2015-12-09 12:27 ` Jan Kara
2015-12-09 15:17 ` Christoph Hellwig
2015-12-21 0:34 ` Dave Chinner
2015-11-24 10:39 ` [PATCH 3/3] ext4/001: Select different output based on mount options Jan Kara
2015-12-07 23:26 ` Theodore Ts'o
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=1448361598-28438-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).