From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/16] btrfs: some cleanups for extent-io-tree (mostly renames)
Date: Mon, 7 Apr 2025 18:36:07 +0100 [thread overview]
Message-ID: <cover.1744046765.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
These are mostly to rename exported functions so that they have a 'btrfs_'
prefix and follow coding style, to avoid potential clashes in the future
with other kernel functions defined elsewhere outside btrfs. As more
functions are added to extent-io-tree.h, there's a tendency to follow the
existing style and not add a 'btrfs_' prefix for consistency with the
other function names, so as time passes we get more exported functions
that don't follow the coding style by missing a 'btrfs_' prefix. I'm in
the process of adding another new exported function to extent-io-tree.h
and found my self unconfortable adding a 'btrfs_' prefix to it while the
other exported functions don't have one.
I tried to split the rename into several and more reasonably sized patches
to make it easier to review and also because a few do a bit more than
simply renaming, but with notes in the change logs.
Filipe Manana (16):
btrfs: remove extent_io_tree_to_inode() and is_inode_io_tree()
btrfs: add btrfs prefix to trace events for extent state alloc and free
btrfs: add btrfs prefix to main lock, try lock and unlock extent functions
btrfs: add btrfs prefix to dio lock and unlock extent functions
btrfs: rename __lock_extent() and __try_lock_extent()
btrfs: rename the functions to clear bits for an extent range
btrfs: rename set_extent_bit() to include a btrfs prefix
btrfs: rename the functions to search for bits in extent ranges
btrfs: rename the functions to get inode and fs_info from an extent io tree
btrfs: directly grab inode at __btrfs_debug_check_extent_io_range()
btrfs: rename the functions to init and release an extent io tree
btrfs: rename the functions to count, test and get bit ranges in io trees
btrfs: rename free_extent_state() to include a btrfs prefix
btrfs: rename remaining exported functions from extent-io-tree.h
btrfs: remove double underscore prefix from __set_extent_bit()
btrfs: make btrfs_find_contiguous_extent_bit() return bool instead of int
fs/btrfs/block-group.c | 34 ++---
fs/btrfs/compression.c | 6 +-
fs/btrfs/defrag.c | 36 ++---
fs/btrfs/dev-replace.c | 12 +-
fs/btrfs/direct-io.c | 38 +++---
fs/btrfs/disk-io.c | 35 ++---
fs/btrfs/extent-io-tree.c | 218 ++++++++++++++-----------------
fs/btrfs/extent-io-tree.h | 155 +++++++++++-----------
fs/btrfs/extent-tree.c | 38 +++---
fs/btrfs/extent_io.c | 40 +++---
fs/btrfs/extent_map.c | 4 +-
fs/btrfs/fiemap.c | 6 +-
fs/btrfs/file-item.c | 22 ++--
fs/btrfs/file.c | 87 ++++++------
fs/btrfs/free-space-cache.c | 36 ++---
fs/btrfs/inode.c | 167 +++++++++++------------
fs/btrfs/ioctl.c | 8 +-
fs/btrfs/ordered-data.c | 8 +-
fs/btrfs/qgroup.c | 30 +++--
fs/btrfs/reflink.c | 12 +-
fs/btrfs/relocation.c | 61 ++++-----
fs/btrfs/super.c | 4 +-
fs/btrfs/tests/btrfs-tests.c | 4 +-
fs/btrfs/tests/extent-io-tests.c | 54 ++++----
fs/btrfs/tests/inode-tests.c | 24 ++--
fs/btrfs/transaction.c | 34 ++---
fs/btrfs/tree-log.c | 12 +-
fs/btrfs/volumes.c | 28 ++--
include/trace/events/btrfs.h | 16 +--
29 files changed, 607 insertions(+), 622 deletions(-)
--
2.45.2
next reply other threads:[~2025-04-07 17:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 17:36 fdmanana [this message]
2025-04-07 17:36 ` [PATCH 01/16] btrfs: remove extent_io_tree_to_inode() and is_inode_io_tree() fdmanana
2025-04-07 18:22 ` David Sterba
2025-04-07 17:36 ` [PATCH 02/16] btrfs: add btrfs prefix to trace events for extent state alloc and free fdmanana
2025-04-07 17:36 ` [PATCH 03/16] btrfs: add btrfs prefix to main lock, try lock and unlock extent functions fdmanana
2025-04-07 17:36 ` [PATCH 04/16] btrfs: add btrfs prefix to dio " fdmanana
2025-04-07 17:36 ` [PATCH 05/16] btrfs: rename __lock_extent() and __try_lock_extent() fdmanana
2025-04-07 17:36 ` [PATCH 06/16] btrfs: rename the functions to clear bits for an extent range fdmanana
2025-04-07 17:36 ` [PATCH 07/16] btrfs: rename set_extent_bit() to include a btrfs prefix fdmanana
2025-04-07 17:36 ` [PATCH 08/16] btrfs: rename the functions to search for bits in extent ranges fdmanana
2025-04-07 17:36 ` [PATCH 09/16] btrfs: rename the functions to get inode and fs_info from an extent io tree fdmanana
2025-04-07 17:36 ` [PATCH 10/16] btrfs: directly grab inode at __btrfs_debug_check_extent_io_range() fdmanana
2025-04-07 17:36 ` [PATCH 11/16] btrfs: rename the functions to init and release an extent io tree fdmanana
2025-04-07 17:36 ` [PATCH 12/16] btrfs: rename the functions to count, test and get bit ranges in io trees fdmanana
2025-04-07 17:36 ` [PATCH 13/16] btrfs: rename free_extent_state() to include a btrfs prefix fdmanana
2025-04-07 17:36 ` [PATCH 14/16] btrfs: rename remaining exported functions from extent-io-tree.h fdmanana
2025-04-07 17:36 ` [PATCH 15/16] btrfs: remove double underscore prefix from __set_extent_bit() fdmanana
2025-04-07 17:36 ` [PATCH 16/16] btrfs: make btrfs_find_contiguous_extent_bit() return bool instead of int fdmanana
2025-04-07 18:24 ` [PATCH 00/16] btrfs: some cleanups for extent-io-tree (mostly renames) David Sterba
2025-04-08 6:24 ` 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=cover.1744046765.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