From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: feng.han@honor.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5 1/2] f2fs: convert F2FS_I_SB to sbi in f2fs_setattr()
Date: Mon, 30 Jun 2025 19:11:47 +0800 [thread overview]
Message-ID: <f9a2bb12-37d4-42a2-b4cc-20959878dfbf@kernel.org> (raw)
In-Reply-To: <20250630095454.3912441-1-wangzijie1@honor.com>
On 6/30/25 17:54, wangzijie wrote:
> Introduce sbi in f2fs_setattr() and convert F2FS_I_SB to it. No logic
> change, just cleanup and prepare to get CAP_BLKS_PER_SEC(sbi).
>
> Signed-off-by: wangzijie <wangzijie1@honor.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, bintian.wang@honor.com,
feng.han@honor.com, niuzhiguo84@gmail.com
Subject: Re: [f2fs-dev] [PATCH v5 1/2] f2fs: convert F2FS_I_SB to sbi in f2fs_setattr()
Date: Mon, 30 Jun 2025 19:11:47 +0800 [thread overview]
Message-ID: <f9a2bb12-37d4-42a2-b4cc-20959878dfbf@kernel.org> (raw)
In-Reply-To: <20250630095454.3912441-1-wangzijie1@honor.com>
On 6/30/25 17:54, wangzijie wrote:
> Introduce sbi in f2fs_setattr() and convert F2FS_I_SB to it. No logic
> change, just cleanup and prepare to get CAP_BLKS_PER_SEC(sbi).
>
> Signed-off-by: wangzijie <wangzijie1@honor.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-06-30 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 9:54 [f2fs-dev] [PATCH v5 1/2] f2fs: convert F2FS_I_SB to sbi in f2fs_setattr() wangzijie
2025-06-30 9:54 ` wangzijie
2025-06-30 9:54 ` [f2fs-dev] [PATCH v5 2/2] f2fs: don't allow unaligned truncation to smaller/equal size on pinned file wangzijie
2025-06-30 9:54 ` wangzijie
2025-06-30 11:12 ` Chao Yu via Linux-f2fs-devel
2025-06-30 11:12 ` Chao Yu
2025-06-30 16:35 ` Jaegeuk Kim via Linux-f2fs-devel
2025-06-30 16:35 ` Jaegeuk Kim
2025-07-01 1:53 ` wangzijie
2025-07-01 1:53 ` wangzijie
2025-06-30 11:11 ` Chao Yu via Linux-f2fs-devel [this message]
2025-06-30 11:11 ` [f2fs-dev] [PATCH v5 1/2] f2fs: convert F2FS_I_SB to sbi in f2fs_setattr() Chao Yu
2025-07-09 18:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-09 18:10 ` patchwork-bot+f2fs
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=f9a2bb12-37d4-42a2-b4cc-20959878dfbf@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzijie1@honor.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 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.