From: Eric Sandeen <sandeen@redhat.com>
To: fstests <fstests@vger.kernel.org>
Subject: [PATCH 0/3] move xfs non-project quota tests to generic
Date: Tue, 20 Sep 2016 17:14:44 -0500 [thread overview]
Message-ID: <65c03ebd-ee9c-7439-2642-0362a177ec6d@redhat.com> (raw)
Now that bleeding edge xfs_quota can support basic operations
on non-xfs filesystems, move some xfs-specific quota tests into
generic/
Project related tests will come later after a bit more cleanup.
Several xfs quota tests can't be generic, as they depend on
various xfs-specific bits like xfs_db or bulkstat.
next reply other threads:[~2016-09-20 22:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 22:14 Eric Sandeen [this message]
2016-09-20 22:15 ` [PATCH 1/3] xfs/260: fix output to match actions Eric Sandeen
2016-09-22 14:07 ` Bill O'Donnell
2016-09-20 22:21 ` [PATCH 2/3] modify xfs/ quota tests to work on generic filesystems Eric Sandeen
2016-09-21 9:37 ` Eryu Guan
2016-09-21 13:02 ` Eric Sandeen
2016-09-21 14:30 ` Eryu Guan
2016-09-21 14:52 ` Eric Sandeen
2016-09-22 14:09 ` Bill O'Donnell
2016-09-22 18:54 ` [PATCH 2/3 V2] " Eric Sandeen
2016-09-22 18:57 ` Bill O'Donnell
2016-09-20 22:24 ` [PATCH 3/3] move now-generic quota tests to generic Eric Sandeen
2016-09-20 23:40 ` Dave Chinner
2016-09-21 1:41 ` Eric Sandeen
2016-09-21 6:44 ` 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=65c03ebd-ee9c-7439-2642-0362a177ec6d@redhat.com \
--to=sandeen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox