From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>,
linux-btrfs@vger.kernel.org, johannes.thumshirn@wdc.com
Subject: Re: [PATCH] btrfs/163: Fix recently broken test
Date: Thu, 24 Sep 2020 20:35:03 +0800 [thread overview]
Message-ID: <27b33a7f-74de-5ae7-fb71-586e36571b7d@oracle.com> (raw)
In-Reply-To: <20200924121910.22477-1-nborisov@suse.com>
On 24/9/20 8:19 pm, Nikolay Borisov wrote:
> Upstream commit "btrfs: fix replace of seed device" broke btrfs/163 as
> it disallowed replacing the seed device. Update the test to account for
> this change in behavior.
>
Related fix has already been submitted here
https://patchwork.kernel.org/patch/11758651/
I think Johannes already picked this.
prev parent reply other threads:[~2020-09-24 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 12:19 [PATCH] btrfs/163: Fix recently broken test Nikolay Borisov
2020-09-24 12:35 ` 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=27b33a7f-74de-5ae7-fb71-586e36571b7d@oracle.com \
--to=anand.jain@oracle.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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