linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 1/2] fstests: btrfs: Make seed device test cases into their own group
Date: Thu, 10 Jan 2019 14:17:27 +0800	[thread overview]
Message-ID: <bf4b36e4-3ca3-86c9-ff6a-5062b1a13e8b@oracle.com> (raw)
In-Reply-To: <20190110061415.32045-1-wqu@suse.com>



On 01/10/2019 02:14 PM, Qu Wenruo wrote:
> btrfs/16[123] are all seed device related test cases, make them into
> 'seed' group.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

Reviewed-by: Anand Jain <anand.jain@oracle.com>

> ---
>   tests/btrfs/group | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/btrfs/group b/tests/btrfs/group
> index b78ed37fd9f1..04c0254aa4bf 100644
> --- a/tests/btrfs/group
> +++ b/tests/btrfs/group
> @@ -163,9 +163,9 @@
>   158 auto quick raid scrub
>   159 auto quick punch log
>   160 auto quick
> -161 auto quick volume
> -162 auto quick volume
> -163 auto quick volume
> +161 auto quick volume seed
> +162 auto quick volume seed
> +163 auto quick volume seed
>   164 auto quick volume
>   165 auto quick subvol
>   166 auto quick qgroup
> 

      parent reply	other threads:[~2019-01-10  6:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10  6:14 [PATCH 1/2] fstests: btrfs: Make seed device test cases into their own group Qu Wenruo
2019-01-10  6:14 ` [PATCH 2/2] fstests: btrfs: Introduce stress test for deadlock between snapshot delete and other read-write operations Qu Wenruo
2019-01-10 12:08   ` Filipe Manana
2019-01-10 13:49     ` Qu Wenruo
2019-01-10 13:53       ` Filipe Manana
2019-01-10 13:59         ` Qu Wenruo
2019-01-10  6:17 ` Anand Jain [this message]

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=bf4b36e4-3ca3-86c9-ff6a-5062b1a13e8b@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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).