From: patchwork-bot+f2fs@kernel.org
To: YH Lin <yhli@google.com>
Cc: yes@google.com, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, linux-f2fs-devel@lists.sourceforge.net,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
jaegeuk@kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: optimize trace_f2fs_write_checkpoint with enums
Date: Tue, 02 Dec 2025 18:10:07 +0000 [thread overview]
Message-ID: <176469900752.3331097.11163063452209234424.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128032509.825003-1-yhli@google.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 28 Nov 2025 11:23:57 +0800 you wrote:
> This patch optimizes the tracepoint by replacing these hardcoded strings
> with a new enumeration f2fs_cp_phase.
>
> 1.Defines enum f2fs_cp_phase with values for each checkpoint phase.
> 2.Updates trace_f2fs_write_checkpoint to accept a u16 phase argument
> instead of a string pointer.
> 3.Uses __print_symbolic in TP_printk to convert the enum values
> back to their corresponding strings for human-readable trace output.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: optimize trace_f2fs_write_checkpoint with enums
https://git.kernel.org/jaegeuk/f2fs/c/a7982944b487
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-12-02 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no>
2025-11-28 3:23 ` [PATCH v2] f2fs: optimize trace_f2fs_write_checkpoint with enums YH Lin
2025-12-02 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=176469900752.3331097.11163063452209234424.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=yes@google.com \
--cc=yhli@google.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