public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] btrfs: some trivial cleanups related to io trees
Date: Wed, 2 Apr 2025 07:52:06 +1030	[thread overview]
Message-ID: <2cd112e3-8b0c-4cff-98b6-5a0f59336d8c@suse.com> (raw)
In-Reply-To: <cover.1743521098.git.fdmanana@suse.com>



在 2025/4/2 01:59, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Some simple cleanups related to io trees that are very trivial and were
> initally part of a larger patchset. Details in the change logs.

My bad, didn't notice the v2 series.

Still looks good.

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

Thanks,
Qu>
> V2: Added patch 3/4.
> 
> Filipe Manana (4):
>    btrfs: use clear_extent_bit() at try_release_extent_state()
>    btrfs: use clear_extent_bits() at chunk_map_device_clear_bits()
>    btrfs: use clear_extent_bits() instead of clear_extent_bit() where possible
>    btrfs: simplify last record detection at test_range_bit_exists()
> 
>   fs/btrfs/extent-io-tree.c    |  8 +++-----
>   fs/btrfs/extent_io.c         |  2 +-
>   fs/btrfs/inode.c             |  3 +--
>   fs/btrfs/reflink.c           |  5 ++---
>   fs/btrfs/tests/inode-tests.c | 24 ++++++++++++------------
>   fs/btrfs/volumes.c           |  7 +++----
>   6 files changed, 22 insertions(+), 27 deletions(-)
> 


  parent reply	other threads:[~2025-04-01 21:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 12:05 [PATCH 0/3] btrfs: some trivial cleanups related to io trees fdmanana
2025-04-01 12:05 ` [PATCH 1/3] btrfs: use clear_extent_bit() at try_release_extent_state() fdmanana
2025-04-01 12:05 ` [PATCH 2/3] btrfs: use clear_extent_bits() at chunk_map_device_clear_bits() fdmanana
2025-04-01 12:05 ` [PATCH 3/3] btrfs: simplify last record detection at test_range_bit_exists() fdmanana
2025-04-01 15:29 ` [PATCH v2 0/4] btrfs: some trivial cleanups related to io trees fdmanana
2025-04-01 15:29   ` [PATCH v2 1/4] btrfs: use clear_extent_bit() at try_release_extent_state() fdmanana
2025-04-01 15:29   ` [PATCH v2 2/4] btrfs: use clear_extent_bits() at chunk_map_device_clear_bits() fdmanana
2025-04-01 15:29   ` [PATCH v2 3/4] btrfs: use clear_extent_bits() instead of clear_extent_bit() where possible fdmanana
2025-04-01 15:29   ` [PATCH v2 4/4] btrfs: simplify last record detection at test_range_bit_exists() fdmanana
2025-04-01 15:46   ` [PATCH v2 0/4] btrfs: some trivial cleanups related to io trees Boris Burkov
2025-04-01 21:22   ` Qu Wenruo [this message]
2025-04-01 21:20 ` [PATCH 0/3] " Qu Wenruo

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=2cd112e3-8b0c-4cff-98b6-5a0f59336d8c@suse.com \
    --to=wqu@suse.com \
    --cc=fdmanana@kernel.org \
    --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