All of lore.kernel.org
 help / color / mirror / Atom feed
From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: some cleanups around read_block_for_search()
Date: Wed, 16 Oct 2024 15:20:19 +0100	[thread overview]
Message-ID: <cover.1729075703.git.fdmanana@suse.com> (raw)

From: Filipe Manana <fdmanana@suse.com>

A set of cleanups around read_block_for_search() and btrfs_verify_level_key(),
mostly simplify arguments and remove redundant arguments and variables.

Filipe Manana (4):
  btrfs: remove redundant level argument from read_block_for_search()
  btrfs: simplify arguments for btrfs_verify_level_key()
  btrfs: remove redundant initialization from btrfs_readahead_tree_block()
  btrfs: remove local generation variable from read_block_for_search()

 fs/btrfs/ctree.c        | 29 ++++++++++++-----------------
 fs/btrfs/extent_io.c    |  1 -
 fs/btrfs/tree-checker.c | 16 ++++++++--------
 fs/btrfs/tree-checker.h |  4 ++--
 4 files changed, 22 insertions(+), 28 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-10-16 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 14:20 fdmanana [this message]
2024-10-16 14:20 ` [PATCH 1/4] btrfs: remove redundant level argument from read_block_for_search() fdmanana
2024-10-16 14:20 ` [PATCH 2/4] btrfs: simplify arguments for btrfs_verify_level_key() fdmanana
2024-10-16 14:20 ` [PATCH 3/4] btrfs: remove redundant initialization from btrfs_readahead_tree_block() fdmanana
2024-10-16 15:49   ` David Sterba
2024-10-16 16:41     ` Filipe Manana
2024-10-16 14:20 ` [PATCH 4/4] btrfs: remove local generation variable from read_block_for_search() fdmanana
2024-10-16 16:00 ` [PATCH 0/4] btrfs: some cleanups around read_block_for_search() 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.1729075703.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.