From: Chao Yu <chao@kernel.org>
To: Sun Ke <sunke32@huawei.com>, fstests@vger.kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net, guan@eryu.me
Subject: Re: [PATCH v3 1/3] generic/042: make a bigger img for f2fs
Date: Thu, 1 Jul 2021 22:39:34 +0800 [thread overview]
Message-ID: <cc9344d8-9bb7-d876-71b1-56937b16338c@kernel.org> (raw)
In-Reply-To: <20210630113736.551843-2-sunke32@huawei.com>
On 2021/6/30 19:37, Sun Ke wrote:
> f2fs-utils 1.9.0 needs at least 38 MB space for f2fs image. However,
> f2fs-utils 1.14.0 needs at least 52 MB. Not sure if it will change again.
> So, just set it to 128M.
>
> Suggested-by: Chao Yu <yuchao0@huawei.com>
> Signed-off-by: Sun Ke <sunke32@huawei.com>
Reviewed-by: Chao Yu <chao@kernel.org>
next prev parent reply other threads:[~2021-07-01 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:37 [PATCH v3 0/3] Resend the three patches Sun Ke
2021-06-30 11:37 ` [PATCH v3 1/3] generic/042: make a bigger img for f2fs Sun Ke
2021-07-01 14:39 ` Chao Yu [this message]
2021-06-30 11:37 ` [PATCH v3 2/3] generic/103: special left calculation " Sun Ke
2021-07-01 14:40 ` Chao Yu
2021-06-30 11:37 ` [PATCH v3 3/3] generic/260: f2fs is also special Sun Ke
2021-07-01 14:41 ` 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=cc9344d8-9bb7-d876-71b1-56937b16338c@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=sunke32@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