From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: remove check-integrity functionality
Date: Fri, 8 Sep 2023 14:42:13 +0800 [thread overview]
Message-ID: <cover.1694154699.git.wqu@suse.com> (raw)
Check-integrity is already marked deprecated, and is going to be removed
in v6.7.
Since we're already at v6.6 cycle, let's finish the cleanup.
This patchset can be fetched from github repo, just in case some patches
are too large for the mailing list.
The removal is based on the 3 entrance functions, and the final one to
cleanup the remaining pieces.
The entrance functions removal is large, but doesn't touch other files.
The last one is the complete opposite, it touches quite some files but
nothing to do with check-integrity.[ch].
Qu Wenruo (4):
btrfs: remove btrfsic_check_bio() function
btrfs: remove btrfsic_mount() function
btrfs: remove btrfsic_unmount() function
btrfs: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY macro
fs/btrfs/Kconfig | 21 -
fs/btrfs/Makefile | 1 -
fs/btrfs/bio.c | 5 -
fs/btrfs/check-integrity.c | 2871 ------------------------------------
fs/btrfs/check-integrity.h | 20 -
fs/btrfs/dev-replace.c | 1 -
fs/btrfs/disk-io.c | 50 -
fs/btrfs/extent_io.c | 1 -
fs/btrfs/fs.h | 27 +-
fs/btrfs/scrub.c | 1 -
fs/btrfs/super.c | 56 -
11 files changed, 11 insertions(+), 3043 deletions(-)
delete mode 100644 fs/btrfs/check-integrity.c
delete mode 100644 fs/btrfs/check-integrity.h
--
2.42.0
next reply other threads:[~2023-09-08 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 6:42 Qu Wenruo [this message]
2023-09-08 6:42 ` [PATCH 1/4] btrfs: remove btrfsic_check_bio() function Qu Wenruo
2023-09-08 6:42 ` [PATCH 2/4] btrfs: remove btrfsic_mount() function Qu Wenruo
2023-09-08 6:42 ` [PATCH 3/4] btrfs: remove btrfsic_unmount() function Qu Wenruo
2023-09-08 6:42 ` [PATCH 4/4] btrfs: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY macro Qu Wenruo
2023-09-08 21:49 ` [PATCH 0/4] btrfs: remove check-integrity functionality 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.1694154699.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 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.