From: Johannes Thumshirn <jthumshirn@suse.de>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 2/6] btrfs: Remove fs_info from struct async_chunk
Date: Thu, 21 Feb 2019 14:07:48 +0100 [thread overview]
Message-ID: <41341b2c-737b-3a11-a0d4-b7787c3d4aed@suse.de> (raw)
In-Reply-To: <20190221115717.5128-3-nborisov@suse.com>
Looks good,
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-02-21 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 11:57 [PATCH v3 0/6] Compress path cleanups Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 1/6] btrfs: Refactor cow_file_range_async Nikolay Borisov
2019-02-21 13:15 ` Johannes Thumshirn
2019-02-21 13:25 ` Nikolay Borisov
2019-02-21 15:07 ` Johannes Thumshirn
2019-02-21 15:09 ` Nikolay Borisov
2019-02-22 18:05 ` David Sterba
2019-02-22 18:13 ` David Sterba
2019-02-21 11:57 ` [PATCH v3 2/6] btrfs: Remove fs_info from struct async_chunk Nikolay Borisov
2019-02-21 13:07 ` Johannes Thumshirn [this message]
2019-02-21 11:57 ` [PATCH v3 3/6] btrfs: Make compress_file_range take only " Nikolay Borisov
2019-02-21 13:07 ` Johannes Thumshirn
2019-02-21 11:57 ` [PATCH v3 4/6] btrfs: Replace clear_extent_bit with unlock_extent Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 5/6] btrfs: Set iotree only once in submit_compressed_extents Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 6/6] btrfs: Factor out common extent locking code " Nikolay Borisov
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=41341b2c-737b-3a11-a0d4-b7787c3d4aed@suse.de \
--to=jthumshirn@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).