From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 1/3] f2fs-tools: remove obsolete fields in struct f2fs_sb_info
Date: Tue, 20 Feb 2024 20:45:35 +0800 [thread overview]
Message-ID: <20240220124537.11531-1-chao@kernel.org> (raw)
No logic change.
Signed-off-by: Chao Yu <chao@kernel.org>
---
fsck/f2fs.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/fsck/f2fs.h b/fsck/f2fs.h
index e31be22..187e73c 100644
--- a/fsck/f2fs.h
+++ b/fsck/f2fs.h
@@ -257,9 +257,6 @@ struct f2fs_sb_info {
struct f2fs_checkpoint *ckpt;
int cur_cp;
- struct list_head orphan_inode_list;
- unsigned int n_orphans;
-
/* basic file system units */
unsigned int log_sectors_per_block; /* log2 sectors per block */
unsigned int log_blocksize; /* log2 block size */
--
2.40.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2024-02-20 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 12:45 Chao Yu [this message]
2024-02-20 12:45 ` [f2fs-dev] [PATCH 2/3] f2fs-tools: use NULL_ADDR macro to instead magic number for cleanup Chao Yu
2024-02-20 12:45 ` [f2fs-dev] [PATCH 3/3] f2fs-tools: print hexadecimal number in log Chao Yu
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=20240220124537.11531-1-chao@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.