From: Chao Yu <chao@kernel.org>
To: Yangyang Zang <zangyangyang66@gmail.com>, zlang@kernel.org
Cc: chao@kernel.org, fstests@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Yangyang Zang <zangyangyang1@xiaomi.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH 1/2] common/config: export F2FS_RESIZE_PROG
Date: Mon, 23 Mar 2026 17:22:59 +0800 [thread overview]
Message-ID: <c0e09f6d-ec4a-4bce-b27a-35af2be5b2de@kernel.org> (raw)
In-Reply-To: <20260319033519.3954784-1-zangyangyang1@xiaomi.com>
On 3/19/26 11:35, Yangyang Zang wrote:
> export F2FS_RESIZE_PROG w/ resize.f2fs, it can be used for resize f2fs.
>
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Cc: Chao Yu <chao@kernel.org>
> Signed-off-by: Yangyang Zang <zangyangyang1@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-03-23 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 3:35 [PATCH 1/2] common/config: export F2FS_RESIZE_PROG Yangyang Zang
2026-03-19 3:35 ` [PATCH 2/2] f2fs/024: add testcase to check resize corrupting root inode Yangyang Zang
2026-03-23 9:35 ` Chao Yu
2026-03-23 9:22 ` Chao Yu [this message]
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=c0e09f6d-ec4a-4bce-b27a-35af2be5b2de@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zangyangyang1@xiaomi.com \
--cc=zangyangyang66@gmail.com \
--cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox