From: Josef Bacik <josef@toxicpanda.com>
To: Johannes Thumshirn <jth@kernel.org>, Eryu Guan <guaneryu@gmail.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH] btrfs/140: use proper helpers to get devid and physical offset for corruption
Date: Fri, 3 Jan 2020 10:42:33 -0500 [thread overview]
Message-ID: <2970a67b-c10b-0038-ef2e-29b42dda107d@toxicpanda.com> (raw)
In-Reply-To: <20200103111810.658-1-jth@kernel.org>
On 1/3/20 6:18 AM, Johannes Thumshirn wrote:
> Similar to fstests commit 1a27bf14ef8b "btrfs/14[23]: Use proper help to
> get both devid and physical offset for corruption." btrfs/140 needs the
> same treatment to pass with updated btrfs-progs.
>
> Signed-off-by: Johannes Thumshirn <jth@kernel.org>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2020-01-03 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 11:18 [PATCH] btrfs/140: use proper helpers to get devid and physical offset for corruption Johannes Thumshirn
2020-01-03 15:42 ` Josef Bacik [this message]
2020-01-06 8:16 ` Eryu Guan
2020-01-06 8:56 ` Qu Wenruo
2020-01-07 7:14 ` Johannes Thumshirn
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=2970a67b-c10b-0038-ef2e-29b42dda107d@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=Damien.LeMoal@wdc.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=jth@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