From: patchwork-bot+f2fs@kernel.org
To: Yangtao Li <frank.li@vivo.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: export ipu policy in debugfs
Date: Tue, 14 Feb 2023 18:10:28 +0000 [thread overview]
Message-ID: <167639822840.3874.759826899218773944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230213141825.22858-1-frank.li@vivo.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 13 Feb 2023 22:18:24 +0800 you wrote:
> Export ipu_policy as a string in debugfs for better readability and
> it can help us better understand some strategies of the file system.
>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> v3:
> - remove unnecessary '\n'
> fs/f2fs/debug.c | 24 ++++++++++++++++++++++++
> fs/f2fs/segment.h | 1 +
> 2 files changed, 25 insertions(+)
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: export ipu policy in debugfs
https://git.kernel.org/jaegeuk/f2fs/c/f2e357893cb7
- [f2fs-dev,v3,2/2] f2fs: replace si->sbi w/ sbi in stat_show()
https://git.kernel.org/jaegeuk/f2fs/c/dda7d77bcd42
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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:[~2023-02-14 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 14:18 [f2fs-dev] [PATCH v3 1/2] f2fs: export ipu policy in debugfs Yangtao Li via Linux-f2fs-devel
2023-02-13 14:18 ` [f2fs-dev] [PATCH v3 2/2] f2fs: replace si->sbi w/ sbi in stat_show() Yangtao Li via Linux-f2fs-devel
2023-02-14 1:29 ` Chao Yu
2023-02-14 1:28 ` [f2fs-dev] [PATCH v3 1/2] f2fs: export ipu policy in debugfs Chao Yu
2023-02-14 18:10 ` patchwork-bot+f2fs [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=167639822840.3874.759826899218773944.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=frank.li@vivo.com \
--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).