From: Eryu Guan <guan@eryu.me>
To: Vladimir Zapolskiy <vladimir@tuxera.com>
Cc: Eryu Guan <guaneryu@gmail.com>, fstests@vger.kernel.org
Subject: Re: [PATCH 0/4] Assign a few generic tests to additional groups
Date: Sun, 12 Apr 2020 19:16:01 +0800 [thread overview]
Message-ID: <20200412111601.GA3923113@desktop> (raw)
In-Reply-To: <20200408135648.5824-1-vladimir@tuxera.com>
On Wed, Apr 08, 2020 at 04:56:44PM +0300, Vladimir Zapolskiy wrote:
> The rationale behind the proposed changes is to correct and improve
> granularity of some generic tests, so it becomes possible to control
> lists of run tests better, if there is given additional information
> about a test environment and tested filesystems.
Thanks for doing this! I think we could group these changes in a single
patch. Could you please resend with a single patch that does all the
group changes?
Thanks,
Eryu
>
> Vladimir Zapolskiy (4):
> Add generic/459 test to freeze group of tests
> Add generic/482 test to thin group of tests
> Add generic/529 test to acl group of tests
> Add generic/530 test to shutdown group of tests
>
> tests/generic/group | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-04-12 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 13:56 [PATCH 0/4] Assign a few generic tests to additional groups Vladimir Zapolskiy
2020-04-08 13:56 ` [PATCH 1/4] Add generic/459 test to freeze group of tests Vladimir Zapolskiy
2020-04-08 13:56 ` [PATCH 2/4] Add generic/482 test to thin " Vladimir Zapolskiy
2020-04-08 13:56 ` [PATCH 3/4] Add generic/529 test to acl " Vladimir Zapolskiy
2020-04-08 13:56 ` [PATCH 4/4] Add generic/530 test to shutdown " Vladimir Zapolskiy
2020-04-12 6:38 ` [PATCH 0/4] Assign a few generic tests to additional groups Zorro Lang
2020-04-12 11:16 ` Eryu Guan [this message]
2020-04-13 7:23 ` Vladimir Zapolskiy
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=20200412111601.GA3923113@desktop \
--to=guan@eryu.me \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=vladimir@tuxera.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