From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: minor cleanups related to extent buffer
Date: Mon, 26 May 2025 13:32:34 +0930 [thread overview]
Message-ID: <cover.1748232037.git.wqu@suse.com> (raw)
The first patch is a cleanup to remove the unused @fs_info parameter
from btrfs_csum_data().
The second patch uses btrfs_csum_data() directly to calculate super
block checksum and avoid use extent buffer helpers.
The final patch enhance btrfs_print_leaf() to be called with temporary
extent buffers in mkfs/convert, which have no eb->leaf populated.
Qu Wenruo (3):
btrfs-progs: remove the unused fs_info parameter for btrfs_csum_data()
btrfs: mkfs: do not use extent buffer to writeback super block
btrfs-progs: enhance btrfs_print_leaf() to handle NULL fs_info
check/main.c | 2 +-
cmds/rescue-chunk-recover.c | 2 +-
cmds/rescue-fix-data-checksum.c | 4 ++--
convert/common.c | 2 +-
convert/main.c | 2 +-
kernel-shared/ctree.c | 4 +---
kernel-shared/disk-io.c | 12 +++++-------
kernel-shared/disk-io.h | 3 +--
kernel-shared/file-item.c | 3 +--
kernel-shared/print-tree.c | 34 +++++++++++++++++----------------
mkfs/common.c | 9 +++------
tune/change-csum.c | 7 +++----
12 files changed, 38 insertions(+), 46 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-26 4:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 4:02 Qu Wenruo [this message]
2025-05-26 4:02 ` [PATCH 1/3] btrfs-progs: remove the unused fs_info parameter for btrfs_csum_data() Qu Wenruo
2025-05-30 13:32 ` David Sterba
2025-05-26 4:02 ` [PATCH 2/3] btrfs: mkfs: do not use extent buffer to writeback super block Qu Wenruo
2025-05-26 4:02 ` [PATCH 3/3] btrfs-progs: enhance btrfs_print_leaf() to handle NULL fs_info Qu Wenruo
2025-05-30 13:43 ` [PATCH 0/3] btrfs-progs: minor cleanups related to extent buffer 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.1748232037.git.wqu@suse.com \
--to=wqu@suse.com \
--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