From: Chao Yu <chao@kernel.org>
To: Daniel Rosenberg <drosen@google.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs-tools: Fix debug size print
Date: Fri, 24 Nov 2023 16:02:52 +0800 [thread overview]
Message-ID: <53283bde-7de1-4513-44d0-c4d90f0aad98@kernel.org> (raw)
In-Reply-To: <20231118020309.1894531-2-drosen@google.com>
On 2023/11/18 10:03, Daniel Rosenberg wrote:
> The conversion from block size to MB in this debug statement assumes a
> block size of 4K. This switches it to properly use the filesystem's
> block size.
>
> Signed-off-by: Daniel Rosenberg <drosen@google.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
next prev parent reply other threads:[~2023-11-24 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 2:03 [f2fs-dev] [PATCH 0/3] F2FS Tools 16K Bug Fixes Daniel Rosenberg via Linux-f2fs-devel
2023-11-18 2:03 ` [f2fs-dev] [PATCH 1/3] f2fs-tools: Fix debug size print Daniel Rosenberg via Linux-f2fs-devel
2023-11-24 8:02 ` Chao Yu [this message]
2023-11-18 2:03 ` [f2fs-dev] [PATCH 2/3] f2fs-tools: Wait for Block Size to initialize Cache Daniel Rosenberg via Linux-f2fs-devel
2023-11-27 1:42 ` Chao Yu
2023-11-28 0:52 ` Daniel Rosenberg via Linux-f2fs-devel
2023-11-28 1:53 ` Chao Yu
2023-11-18 2:03 ` [f2fs-dev] [PATCH 3/3] f2fs-tools: Fix dqb_curspace to reflect blocksize Daniel Rosenberg via Linux-f2fs-devel
2023-11-27 1:42 ` 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=53283bde-7de1-4513-44d0-c4d90f0aad98@kernel.org \
--to=chao@kernel.org \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).