linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Misc cleanups to cached extent
Date: Fri, 4 May 2018 16:54:13 +0800	[thread overview]
Message-ID: <2f30882d-ffc4-404b-eeb0-0b81188b472e@gmx.com> (raw)
In-Reply-To: <1525420047-17397-1-git-send-email-nborisov@suse.com>



On 2018年05月04日 15:47, Nikolay Borisov wrote:
> Here are a couple of cleanups I stumbled upon while looking at the freespace 
> validation code. The first one simplifies btrfs_rmap_block that has an unused 
> parameter. The next 2 patches cleanup the cache_extent apis since they provide
> more than we are actually using (or have ever used).

Under all cases, only insert_cache_extent2() is used, so removing
add_cache_extent2() is completely fine.

> Nikolay Borisov (3):
>   btrfs-progs: Remove devid parameter from btrfs_rmap_block
>   btrfs-progs: Remove add_cache_extent2
>   btrfs-progs: Remove objectid argument from alloc_cache_extent

All of them looks good.

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> 
>  check/main.c   |  2 +-
>  extent-cache.c | 21 ++++-----------------
>  extent-cache.h |  2 --
>  extent-tree.c  | 10 +++++-----
>  volumes.c      |  7 ++-----
>  volumes.h      |  4 ++--
>  6 files changed, 14 insertions(+), 32 deletions(-)
> 

  parent reply	other threads:[~2018-05-04  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  7:47 [PATCH 0/3] Misc cleanups to cached extent Nikolay Borisov
2018-05-04  7:47 ` [PATCH 1/3] btrfs-progs: Remove devid parameter from btrfs_rmap_block Nikolay Borisov
2018-05-04  7:47 ` [PATCH 2/3] btrfs-progs: Remove add_cache_extent2 Nikolay Borisov
2018-05-04  7:47 ` [PATCH 3/3] btrfs-progs: Remove objectid argument from alloc_cache_extent Nikolay Borisov
2018-05-04  8:54 ` Qu Wenruo [this message]
2018-05-08 17:07 ` [PATCH 0/3] Misc cleanups to cached extent David Sterba

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=2f30882d-ffc4-404b-eeb0-0b81188b472e@gmx.com \
    --to=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).