From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2 v5] f2fs: support RO feature
Date: Sat, 5 Jun 2021 07:47:52 +0800 [thread overview]
Message-ID: <a6f00d18-e9a0-42cc-f0af-fe3852b54243@kernel.org> (raw)
In-Reply-To: <YLj+mQJ6IlADZksB@google.com>
On 2021/6/4 0:08, Jaegeuk Kim wrote:
> Given RO feature in superblock, we don't need to check provisioning/reserve
> spaces and SSA area.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
_______________________________________________
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:[~2021-06-04 23:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 19:02 [f2fs-dev] [PATCH 1/2] f2fs: immutable file can have null address in compressed chunk Jaegeuk Kim
2021-05-21 19:02 ` [f2fs-dev] [PATCH 2/2] f2fs: support RO feature Jaegeuk Kim
2021-05-24 11:53 ` Chao Yu
2021-05-24 17:07 ` Jaegeuk Kim
2021-05-25 1:15 ` Chao Yu
2021-05-25 1:45 ` Jaegeuk Kim
2021-05-26 9:42 ` Chao Yu
2021-05-26 13:58 ` Jaegeuk Kim
2021-05-26 15:06 ` Chao Yu
2021-05-26 15:45 ` Jaegeuk Kim
2021-05-26 13:59 ` [f2fs-dev] [PATCH 2/2 v2] " Jaegeuk Kim
2021-05-26 14:06 ` Jaegeuk Kim
2021-05-26 14:43 ` [f2fs-dev] [PATCH 2/2 v3] " Jaegeuk Kim
2021-05-27 1:19 ` Chao Yu
2021-05-27 1:36 ` Jaegeuk Kim
2021-05-28 2:07 ` Chao Yu
2021-06-02 15:16 ` Chao Yu
2021-06-02 19:02 ` [f2fs-dev] [PATCH 2/2 v4] " Jaegeuk Kim
2021-06-03 15:52 ` Chao Yu
2021-06-03 16:08 ` [f2fs-dev] [PATCH 2/2 v5] " Jaegeuk Kim
2021-06-04 23:47 ` Chao Yu [this message]
2021-05-26 9:08 ` [f2fs-dev] [PATCH 1/2] f2fs: immutable file can have null address in compressed chunk Chao Yu
2021-05-26 14:02 ` Jaegeuk Kim
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=a6f00d18-e9a0-42cc-f0af-fe3852b54243@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).