From: Zhang Qilong via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: <jaegeuk@kernel.org>, <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH -next 3/4] f2fs: rename f2fs_update_extent_tree_range_compressed
Date: Wed, 21 Sep 2022 15:57:36 +0800 [thread overview]
Message-ID: <20220921075737.36708-4-zhangqilong3@huawei.com> (raw)
In-Reply-To: <20220921075737.36708-1-zhangqilong3@huawei.com>
f2fs_update_extent_tree_range_compressed caches both of compressed
and no-compressed extent entry, so we should getting rid of the
"compressed" word will be more appropriate. And we just rename it to
f2fs_readonly_update_extent_tree_range.
Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
---
fs/f2fs/extent_cache.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/extent_cache.c b/fs/f2fs/extent_cache.c
index 7e39381edca0..c59a0ec41e69 100644
--- a/fs/f2fs/extent_cache.c
+++ b/fs/f2fs/extent_cache.c
@@ -663,7 +663,7 @@ static void f2fs_update_extent_tree_range(struct inode *inode,
}
#ifdef CONFIG_F2FS_FS_COMPRESSION
-static void f2fs_update_extent_tree_range_compressed(struct inode *inode,
+static void f2fs_readonly_update_extent_tree_range(struct inode *inode,
pgoff_t fofs, block_t blkaddr, unsigned int llen,
unsigned int c_len)
{
@@ -774,8 +774,8 @@ void f2fs_readonly_update_extent_cache(struct dnode_of_data *dn,
llen = f2fs_normal_blocks_are_contiguous(dn);
}
- f2fs_update_extent_tree_range_compressed(dn->inode,
- index, blkaddr, llen, c_len);
+ f2fs_readonly_update_extent_tree_range(dn->inode, index,
+ blkaddr, llen, c_len);
}
#endif
--
2.25.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-09-21 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 7:57 [f2fs-dev] [PATCH -next 0/4] rebuild compressed extent and support Zhang Qilong via Linux-f2fs-devel
2022-09-21 7:57 ` [f2fs-dev] [PATCH -next 1/4] f2fs: rebuild compressed extent cache update code for readonly-fs Zhang Qilong via Linux-f2fs-devel
2022-09-21 7:57 ` [f2fs-dev] [PATCH -next 2/4] f2fs: extent cache: support extent for no-compressed file Zhang Qilong via Linux-f2fs-devel
2022-09-21 10:40 ` Chao Yu
2022-09-21 7:57 ` Zhang Qilong via Linux-f2fs-devel [this message]
2022-09-21 7:57 ` [f2fs-dev] [PATCH -next 4/4] f2fs: remove the limit and no-compressed file could use extent Zhang Qilong via Linux-f2fs-devel
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=20220921075737.36708-4-zhangqilong3@huawei.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=zhangqilong3@huawei.com \
/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).