From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org, jeffm@suse.com
Subject: Re: [PATCH 0/3] Cleanups around extent increment
Date: Tue, 19 Jun 2018 15:35:08 +0200 [thread overview]
Message-ID: <20180619133508.GO24375@twin.jikos.cz> (raw)
In-Reply-To: <1529323166-29931-1-git-send-email-nborisov@suse.com>
On Mon, Jun 18, 2018 at 02:59:23PM +0300, Nikolay Borisov wrote:
> This series improves the functions involved around extent reference increment.
> The first patch just removes a redundant argument, the second one documents the
> parameters of __btrfs_inc_extent_ref. It can be considered v2 of the standalone
> version which Jeff had some input to. The final patch fixes a comment in
> lookup_inline_extent_backref which transpired while Jeff was revieweing the
> documentation patch.
>
> Nikolay Borisov (3):
> btrfs: Remove fs_info argument from __btrfs_inc_extent_ref
> btrfs: Document __btrfs_inc_extent_ref
> btrfs: Fix comment in lookup_inline_extent_backref
2 and 3 added to misc-next, thanks.
prev parent reply other threads:[~2018-06-19 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 11:59 [PATCH 0/3] Cleanups around extent increment Nikolay Borisov
2018-06-18 11:59 ` [PATCH 1/3] btrfs: Remove fs_info argument from __btrfs_inc_extent_ref Nikolay Borisov
2018-06-19 5:24 ` Qu Wenruo
2018-06-19 13:01 ` Nikolay Borisov
2018-06-19 19:31 ` Jeff Mahoney
2018-06-19 22:36 ` Nikolay Borisov
2018-06-18 11:59 ` [PATCH 2/3] btrfs: Document __btrfs_inc_extent_ref Nikolay Borisov
2018-06-19 5:28 ` Qu Wenruo
2018-06-18 11:59 ` [PATCH 3/3] btrfs: Fix comment in lookup_inline_extent_backref Nikolay Borisov
2018-06-19 13:35 ` David Sterba [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=20180619133508.GO24375@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=jeffm@suse.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