All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] btrfs: rename exported functions from extent_map.h
Date: Tue,  8 Apr 2025 18:32:53 +0100	[thread overview]
Message-ID: <cover.1744130413.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

Many of the exported functions from extent_map.h don't have a 'btrfs_'
prefix, but some have, making it inconsistent and also against the coding
style conventions. I've added myself some of them recently, to get and set
compression on an extent map, and ended up not adding the prefix since the
other functions in the file didn't have the prefix, just to make things
consistent. So rename the ones without the prefix to have it.

I've split this into more reasonably sized patches to avoid having a huge
patch and make things easier to review.

Filipe Manana (6):
  btrfs: rename exported extent map compression functions
  btrfs: rename extent map functions to get block start, end and check if in tree
  btrfs: rename functions to allocate and free extent maps
  btrfs: rename remaining exported extent map functions
  btrfs: rename __lookup_extent_mapping() to remove double underscore prefix
  btrfs: rename __tree_search() to remove double underscore prefix

 fs/btrfs/compression.c            |  18 ++--
 fs/btrfs/defrag.c                 |  22 ++--
 fs/btrfs/direct-io.c              |  26 ++---
 fs/btrfs/disk-io.c                |   2 +-
 fs/btrfs/extent_io.c              |  45 +++++----
 fs/btrfs/extent_map.c             | 163 +++++++++++++++---------------
 fs/btrfs/extent_map.h             |  47 ++++-----
 fs/btrfs/file-item.c              |   4 +-
 fs/btrfs/file.c                   |  30 +++---
 fs/btrfs/inode.c                  |  80 +++++++--------
 fs/btrfs/relocation.c             |   4 +-
 fs/btrfs/super.c                  |   4 +-
 fs/btrfs/tests/extent-map-tests.c | 102 +++++++++----------
 fs/btrfs/tests/inode-tests.c      |  79 ++++++++-------
 fs/btrfs/tree-log.c               |  16 +--
 fs/btrfs/zoned.c                  |  10 +-
 16 files changed, 327 insertions(+), 325 deletions(-)

-- 
2.45.2


             reply	other threads:[~2025-04-08 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 17:32 fdmanana [this message]
2025-04-08 17:32 ` [PATCH 1/6] btrfs: rename exported extent map compression functions fdmanana
2025-04-08 17:32 ` [PATCH 2/6] btrfs: rename extent map functions to get block start, end and check if in tree fdmanana
2025-04-08 17:32 ` [PATCH 3/6] btrfs: rename functions to allocate and free extent maps fdmanana
2025-04-08 17:32 ` [PATCH 4/6] btrfs: rename remaining exported extent map functions fdmanana
2025-04-08 17:32 ` [PATCH 5/6] btrfs: rename __lookup_extent_mapping() to remove double underscore prefix fdmanana
2025-04-08 17:32 ` [PATCH 6/6] btrfs: rename __tree_search() " fdmanana
2025-04-08 22:23 ` [PATCH 0/6] btrfs: rename exported functions from extent_map.h 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.1744130413.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.