public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Eryu Guan <guaneryu@gmail.com>, Johannes Thumshirn <jth@kernel.org>
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: Mon, 6 Jan 2020 16:56:10 +0800	[thread overview]
Message-ID: <1c1dd1ae-e484-ee02-a7d8-077f95f7d4cf@gmx.com> (raw)
In-Reply-To: <20200106081647.GE893866@desktop>


[-- Attachment #1.1: Type: text/plain, Size: 677 bytes --]



On 2020/1/6 下午4:16, Eryu Guan wrote:
> On Fri, Jan 03, 2020 at 12:18:10PM +0100, 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>
>> ---
> 
> Qu Wenruo has posted "fstests: btrfs/14[01]: Use proper helper to get
> both devid and physical for corruption" earlier, and I'll apply his
> patch instead.

Thanks.

The timing is great since I was just going to ping that patch.

Thanks,
Qu
> 
> Thanks,
> Eryu
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]

  reply	other threads:[~2020-01-06  8:56 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
2020-01-06  8:16 ` Eryu Guan
2020-01-06  8:56   ` Qu Wenruo [this message]
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=1c1dd1ae-e484-ee02-a7d8-077f95f7d4cf@gmx.com \
    --to=quwenruo.btrfs@gmx.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