From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: ordered extent csum list related cleanup
Date: Tue, 10 Feb 2026 13:54:28 +1030 [thread overview]
Message-ID: <cover.1770693583.git.wqu@suse.com> (raw)
Trivial changes, please refer to the commit message of each patch.
Qu Wenruo (3):
btrfs: rename btrfs_ordered_extent::list to csum_list
btrfs: make add_pending_csums() to take an ordered extent as parameter
btrfs: rename btrfs_csum_file_blocks() to btrfs_insert_data_csums()
fs/btrfs/file-item.c | 6 +++---
fs/btrfs/file-item.h | 6 +++---
fs/btrfs/inode.c | 18 ++++++++++--------
fs/btrfs/ordered-data.c | 10 +++++-----
fs/btrfs/ordered-data.h | 2 +-
fs/btrfs/tree-log.c | 8 ++++----
fs/btrfs/zoned.c | 7 +++----
7 files changed, 29 insertions(+), 28 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-10 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 3:24 Qu Wenruo [this message]
2026-02-10 3:24 ` [PATCH 1/3] btrfs: rename btrfs_ordered_extent::list to csum_list Qu Wenruo
2026-02-10 3:24 ` [PATCH 2/3] btrfs: make add_pending_csums() to take an ordered extent as parameter Qu Wenruo
2026-02-10 3:24 ` [PATCH 3/3] btrfs: rename btrfs_csum_file_blocks() to btrfs_insert_data_csums() Qu Wenruo
2026-02-10 12:47 ` [PATCH 0/3] btrfs: ordered extent csum list related cleanup Filipe Manana
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.1770693583.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