From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/16] btrfs: remove fs_info argument from space_info functions
Date: Mon, 13 Oct 2025 18:37:55 +0100 [thread overview]
Message-ID: <cover.1760376569.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
We don't need to pass fs_info since we can grab it from a space_info.
More details in the changelog, trivial patchset.
Filipe Manana (16):
btrfs: remove fs_info argument from btrfs_try_granting_tickets()
btrfs: remove fs_info argument from priority_reclaim_data_space()
btrfs: remove fs_info argument from priority_reclaim_metadata_space()
btrfs: remove fs_info argument from maybe_fail_all_tickets()
btrfs: remove fs_info argument from calc_available_free_space()
btrfs: remove fs_info argument from btrfs_can_overcommit()
btrfs: remove fs_info argument from btrfs_dump_space_info()
btrfs: remove fs_info argument from shrink_delalloc() and flush_space()
btrfs: remove fs_info argument from btrfs_calc_reclaim_metadata_size()
btrfs: remove fs_info argument from need_preemptive_reclaim()
btrfs: remove fs_info argument from steal_from_global_rsv()
btrfs: remove fs_info argument from handle_reserve_ticket()
btrfs: remove fs_info argument from maybe_clamp_preempt()
btrfs: fix parameter documentation for btrfs_reserve_data_bytes()
btrfs: remove fs_info argument from __reserve_bytes()
btrfs: remove fs_info argument from btrfs_reserve_metadata_bytes()
fs/btrfs/block-group.c | 15 ++--
fs/btrfs/block-rsv.c | 14 ++--
fs/btrfs/delalloc-space.c | 4 +-
fs/btrfs/delayed-ref.c | 2 +-
fs/btrfs/extent-tree.c | 3 +-
fs/btrfs/space-info.c | 168 +++++++++++++++++---------------------
fs/btrfs/space-info.h | 14 ++--
fs/btrfs/transaction.c | 4 +-
8 files changed, 101 insertions(+), 123 deletions(-)
--
2.47.2
next reply other threads:[~2025-10-13 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 17:37 fdmanana [this message]
2025-10-13 17:37 ` [PATCH 01/16] btrfs: remove fs_info argument from btrfs_try_granting_tickets() fdmanana
2025-10-13 17:37 ` [PATCH 02/16] btrfs: remove fs_info argument from priority_reclaim_data_space() fdmanana
2025-10-13 17:37 ` [PATCH 03/16] btrfs: remove fs_info argument from priority_reclaim_metadata_space() fdmanana
2025-10-13 17:37 ` [PATCH 04/16] btrfs: remove fs_info argument from maybe_fail_all_tickets() fdmanana
2025-10-13 17:38 ` [PATCH 05/16] btrfs: remove fs_info argument from calc_available_free_space() fdmanana
2025-10-13 17:38 ` [PATCH 06/16] btrfs: remove fs_info argument from btrfs_can_overcommit() fdmanana
2025-10-13 17:38 ` [PATCH 07/16] btrfs: remove fs_info argument from btrfs_dump_space_info() fdmanana
2025-10-13 17:38 ` [PATCH 08/16] btrfs: remove fs_info argument from shrink_delalloc() and flush_space() fdmanana
2025-10-13 17:38 ` [PATCH 09/16] btrfs: remove fs_info argument from btrfs_calc_reclaim_metadata_size() fdmanana
2025-10-13 17:38 ` [PATCH 10/16] btrfs: remove fs_info argument from need_preemptive_reclaim() fdmanana
2025-10-13 17:38 ` [PATCH 11/16] btrfs: remove fs_info argument from steal_from_global_rsv() fdmanana
2025-10-13 17:38 ` [PATCH 12/16] btrfs: remove fs_info argument from handle_reserve_ticket() fdmanana
2025-10-13 17:38 ` [PATCH 13/16] btrfs: remove fs_info argument from maybe_clamp_preempt() fdmanana
2025-10-13 17:38 ` [PATCH 14/16] btrfs: fix parameter documentation for btrfs_reserve_data_bytes() fdmanana
2025-10-13 17:38 ` [PATCH 15/16] btrfs: remove fs_info argument from __reserve_bytes() fdmanana
2025-10-13 17:38 ` [PATCH 16/16] btrfs: remove fs_info argument from btrfs_reserve_metadata_bytes() fdmanana
2025-10-13 21:28 ` [PATCH 00/16] btrfs: remove fs_info argument from space_info functions Qu Wenruo
2025-10-14 7:08 ` Johannes Thumshirn
2025-10-15 8:59 ` Anand Jain
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.1760376569.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.