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 3/3] f2fs: add a sysfs entry to show zone capacity
Date: Sun, 17 Jul 2022 15:23:48 +0800 [thread overview]
Message-ID: <c265cef1-de1d-5077-6727-d965ecd10fa9@kernel.org> (raw)
In-Reply-To: <20220628234733.3330502-3-jaegeuk@kernel.org>
On 2022/6/29 7:47, Jaegeuk Kim wrote:
> This patch adds a sysfs entry showing the unusable space in a section
> made by zone capacity.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
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
next prev parent reply other threads:[~2022-07-17 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 23:47 [f2fs-dev] [PATCH 1/3] f2fs: enforce single zone capacity Jaegeuk Kim
2022-06-28 23:47 ` [f2fs-dev] [PATCH 2/3] f2fs: adjust zone capacity when considering valid block count Jaegeuk Kim
2022-07-17 7:23 ` Chao Yu
2022-06-28 23:47 ` [f2fs-dev] [PATCH 3/3] f2fs: add a sysfs entry to show zone capacity Jaegeuk Kim
2022-07-17 7:23 ` Chao Yu [this message]
2022-07-17 7:22 ` [f2fs-dev] [PATCH 1/3] f2fs: enforce single " 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=c265cef1-de1d-5077-6727-d965ecd10fa9@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).