All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/8] btrfs: some trivial cleanups
Date: Fri,  7 Mar 2025 13:44:17 +0000	[thread overview]
Message-ID: <cover.1741354476.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

A group of trivial cleanups that started with making log tree code
less verbose while fixing a couple bugs, by removing repeated BTRFS_I()
calls, and then extended to btrfs_iget() and removing redundant arguments
from a few functions. Details in the change logs.

Filipe Manana (8):
  btrfs: return a btrfs_inode from btrfs_iget_logging()
  btrfs: return a btrfs_inode from read_one_inode()
  btrfs: pass a btrfs_inode to fixup_inode_link_count()
  btrfs: make btrfs_iget() return a btrfs inode instead
  btrfs: make btrfs_iget_path() return a btrfs inode instead
  btrfs: remove unnecessary fs_info argument from create_reloc_inode()
  btrfs: remove unnecessary fs_info argument from delete_block_group_cache()
  btrfs: remove unnecessary fs_info argument from btrfs_add_block_group_cache()

 fs/btrfs/block-group.c      |  16 +--
 fs/btrfs/btrfs_inode.h      |   6 +-
 fs/btrfs/defrag.c           |  14 +-
 fs/btrfs/export.c           |  17 ++-
 fs/btrfs/free-space-cache.c |  10 +-
 fs/btrfs/inode.c            |  64 ++++-----
 fs/btrfs/ioctl.c            |   7 +-
 fs/btrfs/relocation.c       |  30 +++--
 fs/btrfs/send.c             |  25 ++--
 fs/btrfs/super.c            |   4 +-
 fs/btrfs/tree-log.c         | 261 +++++++++++++++++-------------------
 11 files changed, 225 insertions(+), 229 deletions(-)

-- 
2.45.2


             reply	other threads:[~2025-03-07 13:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 13:44 fdmanana [this message]
2025-03-07 13:44 ` [PATCH 1/8] btrfs: return a btrfs_inode from btrfs_iget_logging() fdmanana
2025-03-07 13:44 ` [PATCH 2/8] btrfs: return a btrfs_inode from read_one_inode() fdmanana
2025-03-07 13:44 ` [PATCH 3/8] btrfs: pass a btrfs_inode to fixup_inode_link_count() fdmanana
2025-03-07 13:44 ` [PATCH 4/8] btrfs: make btrfs_iget() return a btrfs inode instead fdmanana
2025-03-08 15:31   ` kernel test robot
2025-03-10 10:45     ` Filipe Manana
2025-03-11  9:40       ` Philip Li
2025-03-08 17:48   ` kernel test robot
2025-03-10 10:46     ` Filipe Manana
2025-03-07 13:44 ` [PATCH 5/8] btrfs: make btrfs_iget_path() " fdmanana
2025-03-07 13:44 ` [PATCH 6/8] btrfs: remove unnecessary fs_info argument from create_reloc_inode() fdmanana
2025-03-07 13:44 ` [PATCH 7/8] btrfs: remove unnecessary fs_info argument from delete_block_group_cache() fdmanana
2025-03-07 13:44 ` [PATCH 8/8] btrfs: remove unnecessary fs_info argument from btrfs_add_block_group_cache() fdmanana
2025-03-10 18:42 ` [PATCH 0/8] btrfs: some trivial cleanups 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.1741354476.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.