From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong@oppo.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs-tools: print extension list properly
Date: Tue, 9 Apr 2024 11:26:40 +0800 [thread overview]
Message-ID: <98c1738a-9a83-49d2-a877-0856209203dd@kernel.org> (raw)
In-Reply-To: <20240408131140.4100090-1-shengyong@oppo.com>
On 2024/4/8 21:11, Sheng Yong wrote:
> The "hot file extensions" list does not print properly.
>
> **Before**
>
> extension_count [0x 23 : 35]
> cold file extentsions
> [mp wm og jp ]
> [avi m4v m4p mkv ]
> [mov webm wav m4a ]
> [3gp opus flac gif ]
> [png svg webp jar ]
> [deb iso gz xz ]
> [zst pdf pyc ttc ]
> [ttf exe apk cnt ]
> [exo odex vdex ]
> hot_ext_count [0x 1 : 1]
> hot file extentsions
> db ]
> cp_payload [0x 0 : 0]
>
> **After**
>
> extension_count [0x 23 : 35]
> cold file extentsions
> [mp wm og jp ]
> [avi m4v m4p mkv ]
> [mov webm wav m4a ]
> [3gp opus flac gif ]
> [png svg webp jar ]
> [deb iso gz xz ]
> [zst pdf pyc ttc ]
> [ttf exe apk cnt ]
> [exo odex vdex ]
> hot_ext_count [0x 1 : 1]
> hot file extentsions
> [db ]
> cp_payload [0x 0 : 0]
>
> Signed-off-by: Sheng Yong <shengyong@oppo.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
prev parent reply other threads:[~2024-04-09 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 13:11 [f2fs-dev] [PATCH] f2fs-tools: print extension list properly Sheng Yong via Linux-f2fs-devel
2024-04-09 3:26 ` 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=98c1738a-9a83-49d2-a877-0856209203dd@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=shengyong@oppo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).