From: Anand Jain <anand.jain@oracle.com>
To: Josef Bacik <josef@toxicpanda.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs_show_devname don't traverse into the seed fsid
Date: Fri, 10 Jul 2020 23:16:04 +0800 [thread overview]
Message-ID: <e66f6a5b-9790-b545-b5ee-8e1ce007b0cc@oracle.com> (raw)
In-Reply-To: <68bd59f6-8817-f682-1570-ad2131086ac8@toxicpanda.com>
>
> This needs to come with an xfstest so we do not regress this in the
> future. Thanks,
Oh yes. Makes sense. An xfstests test case is on its way.
Thanks, Anand
>
> Josef
next prev parent reply other threads:[~2020-07-10 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 6:37 [PATCH] btrfs_show_devname don't traverse into the seed fsid Anand Jain
2020-07-10 14:32 ` Josef Bacik
2020-07-10 15:16 ` Anand Jain [this message]
2020-07-10 15:54 ` Martin K. Petersen
2020-07-13 5:48 ` [PATCH] fstests: btrfs test if show_devname returns sprout device Anand Jain
2020-07-13 7:03 ` Nikolay Borisov
2020-07-13 11:00 ` [PATCH v2] " Anand Jain
2020-07-13 11:15 ` Nikolay Borisov
2020-07-13 11:32 ` Anand Jain
2020-07-19 15:19 ` Eryu Guan
2020-07-20 3:55 ` [PATCH v3] " Anand Jain
2020-07-13 14:04 ` [PATCH] btrfs_show_devname don't traverse into the seed fsid Nikolay Borisov
2020-07-15 10:21 ` David Sterba
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=e66f6a5b-9790-b545-b5ee-8e1ce007b0cc@oracle.com \
--to=anand.jain@oracle.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@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).