From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: some cleanups related to io trees
Date: Fri, 28 Mar 2025 14:24:01 +0000 [thread overview]
Message-ID: <cover.1743166248.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Remove some no longer used/needed code related to io trees.
Details in the change logs.
Filipe Manana (3):
btrfs: remove leftover EXTENT_UPTODATE clear from an inode's io_tree
btrfs: stop searching for EXTENT_DIRTY bit in the excluded extents io tree
btrfs: remove EXTENT_UPTODATE io tree flag
fs/btrfs/block-group.c | 9 ++++-----
fs/btrfs/extent-io-tree.h | 8 --------
fs/btrfs/inode.c | 22 ++++++++++------------
fs/btrfs/relocation.c | 3 ---
fs/btrfs/tests/extent-io-tests.c | 1 -
fs/btrfs/tests/inode-tests.c | 12 ++++--------
include/trace/events/btrfs.h | 1 -
7 files changed, 18 insertions(+), 38 deletions(-)
--
2.45.2
next reply other threads:[~2025-03-28 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 14:24 fdmanana [this message]
2025-03-28 14:24 ` [PATCH 1/3] btrfs: remove leftover EXTENT_UPTODATE clear from an inode's io_tree fdmanana
2025-03-28 14:24 ` [PATCH 2/3] btrfs: stop searching for EXTENT_DIRTY bit in the excluded extents io tree fdmanana
2025-03-28 14:24 ` [PATCH 3/3] btrfs: remove EXTENT_UPTODATE io tree flag fdmanana
2025-03-28 16:30 ` [PATCH 0/3] btrfs: some cleanups related to io trees Boris Burkov
2025-03-28 17:23 ` 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=cover.1743166248.git.fdmanana@suse.com \
--to=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