From: Kemeng Shi <shikemeng@huaweicloud.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
shikemeng@huaweicloud.com, linfeilong@huawei.com
Subject: [PATCH 0/4] Remove unused group parameter in bitmap checksum
Date: Wed, 22 Feb 2023 04:30:23 +0800 [thread overview]
Message-ID: <20230221203027.2359920-1-shikemeng@huaweicloud.com> (raw)
Hi all, this series try to remove unused group parameter in four bitmap
checksum functions. Each function is cleaned in a separated patch.
Thanks!
Kemeng Shi (4):
ext4: remove unused group parameter in ext4_inode_bitmap_csum_verify
ext4: remove unused group parameter in ext4_inode_bitmap_csum_set
ext4: remove unused group parameter in ext4_block_bitmap_csum_verify
ext4: remove unused group parameter in ext4_block_bitmap_csum_set
fs/ext4/balloc.c | 3 +--
fs/ext4/bitmap.c | 8 ++++----
fs/ext4/ext4.h | 8 ++++----
fs/ext4/ialloc.c | 14 ++++++--------
fs/ext4/mballoc.c | 10 +++++-----
fs/ext4/resize.c | 7 +++----
6 files changed, 23 insertions(+), 27 deletions(-)
--
2.30.0
next reply other threads:[~2023-02-21 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 20:30 Kemeng Shi [this message]
2023-02-21 20:30 ` [PATCH 1/4] ext4: remove unused group parameter in ext4_inode_bitmap_csum_verify Kemeng Shi
2023-03-07 11:07 ` Jan Kara
2023-02-21 20:30 ` [PATCH 2/4] ext4: remove unused group parameter in ext4_inode_bitmap_csum_set Kemeng Shi
2023-03-07 11:08 ` Jan Kara
2023-02-21 20:30 ` [PATCH 3/4] ext4: remove unused group parameter in ext4_block_bitmap_csum_verify Kemeng Shi
2023-03-07 11:08 ` Jan Kara
2023-02-21 20:30 ` [PATCH 4/4] ext4: remove unused group parameter in ext4_block_bitmap_csum_set Kemeng Shi
2023-03-07 11:09 ` Jan Kara
2023-03-17 1:52 ` [PATCH 0/4] Remove unused group parameter in bitmap checksum Theodore Ts'o
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=20230221203027.2359920-1-shikemeng@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=linfeilong@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).