From: Nikolay Borisov <nborisov@suse.com>
To: Johannes Thumshirn <jthumshirn@suse.de>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 3/6] btrfs: Make compress_file_range take only struct async_cow
Date: Thu, 21 Feb 2019 13:55:06 +0200 [thread overview]
Message-ID: <010a648e-4c75-39ff-8add-87c45a19a383@suse.com> (raw)
In-Reply-To: <559c44a0-5b82-8fea-3d46-8f5d9e9bb2f3@suse.de>
On 20.02.19 г. 17:27 ч., Johannes Thumshirn wrote:
> Hmm "... and num_added" for the Subject?
Nah, that's obvious, the focus here is instead of taking 4-5 more
arguments they are replaced with async_cow.
next prev parent reply other threads:[~2019-02-21 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 15:11 [PATCH v2 0/6] Compressed path cleanups Nikolay Borisov
2019-02-20 15:11 ` [PATCH v2 1/6] btrfs: Refactor cow_file_range_async Nikolay Borisov
2019-02-20 15:51 ` Johannes Thumshirn
2019-02-20 15:11 ` [PATCH v2 2/6] btrfs: Remove fs_info from struct async_cow Nikolay Borisov
2019-02-20 15:25 ` Johannes Thumshirn
2019-02-20 15:29 ` Nikolay Borisov
2019-02-20 15:11 ` [PATCH v2 3/6] btrfs: Make compress_file_range take only " Nikolay Borisov
2019-02-20 15:27 ` Johannes Thumshirn
2019-02-21 11:55 ` Nikolay Borisov [this message]
2019-02-21 13:08 ` Johannes Thumshirn
2019-02-20 15:11 ` [PATCH v2 4/6] btrfs: Replace clear_extent_bit with unlock_extent Nikolay Borisov
2019-02-20 15:29 ` Johannes Thumshirn
2019-02-20 15:11 ` [PATCH v2 5/6] btrfs: Set iotree only once in submit_compressed_extents Nikolay Borisov
2019-02-20 15:33 ` Johannes Thumshirn
2019-02-20 15:11 ` [PATCH v2 6/6] btrfs: Factor out common extent locking code " Nikolay Borisov
2019-02-20 15:35 ` 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=010a648e-4c75-39ff-8add-87c45a19a383@suse.com \
--to=nborisov@suse.com \
--cc=jthumshirn@suse.de \
--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).