From: Stefan Behrens <sbehrens@giantdisaster.de>
To: linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
xfs@oss.sgi.com
Subject: [PATCH v3 0/2] xfstests: Changed a couple of tests to be generic
Date: Mon, 1 Aug 2011 12:31:18 +0200 [thread overview]
Message-ID: <cover.1312193821.git.sbehrens@giantdisaster.de> (raw)
Changes v2->v3:
- Merged 3 patches into one.
- Less verbose subject lines.
Changes v1->v2:
- Instead of just adding btrfs to the list of supported filesystems,
the 7 tests that are touched by this patch series are now executed
for all filesystems (since the tests are generic ones).
- The changes in src/t_immutable.c are revised to make the setting
of append-only and immutable flags generic instead of just adding
code for btrfs.
This patch series changes the tests 015, 062, 079, 083, 117, 120 and
192 to be generic for all filesystems and to be executed for all
filesystems.
For test 079 to run, src/t_immutable.c was also modified to use the
new generic FS_IOC_SETFLAGS/FS_IOC_GETFLAGS ioctl() if they are
available.
Stefan Behrens (2):
xfstests: make more tests generic
xfstests: make t_immutable and 079 filesystem-agnostic
015 | 5 ++-
062 | 4 +-
062.out | 6 -----
079 | 12 +++++++--
083 | 12 +++++++--
117 | 4 +-
120 | 4 +-
192 | 2 +-
src/t_immutable.c | 66 +++++++++++++++++-----------------------------------
9 files changed, 50 insertions(+), 65 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-08-01 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 10:31 Stefan Behrens [this message]
2011-08-01 10:31 ` [PATCH v3 1/2] xfstests: make more tests generic Stefan Behrens
2011-08-10 15:52 ` David Sterba
2011-08-10 16:33 ` Christoph Hellwig
2011-08-10 16:38 ` Alex Elder
2011-08-10 16:36 ` Alex Elder
2011-08-10 16:43 ` Christoph Hellwig
2011-08-01 10:31 ` [PATCH v3 2/2] xfstests: make t_immutable and 079 filesystem-agnostic Stefan Behrens
2011-08-01 11:03 ` [PATCH v3 0/2] xfstests: Changed a couple of tests to be generic Christoph Hellwig
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=cover.1312193821.git.sbehrens@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).