From: patchwork-bot+f2fs@kernel.org
To: Douglas RAILLARD <douglas.raillard@arm.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, rostedt@goodmis.org,
mhiramat@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event
Date: Tue, 07 Mar 2023 17:40:24 +0000 [thread overview]
Message-ID: <167821082479.1693.18260840022075703789.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230306122549.236561-1-douglas.raillard@arm.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 6 Mar 2023 12:25:49 +0000 you wrote:
> From: Douglas Raillard <douglas.raillard@arm.com>
>
> Fix the nid_t field so that its size is correctly reported in the text
> format embedded in trace.dat files. As it stands, it is reported as
> being of size 4:
>
> field:nid_t nid[3]; offset:24; size:4; signed:0;
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: Fix f2fs_truncate_partial_nodes ftrace event
https://git.kernel.org/jaegeuk/f2fs/c/3ccc99d5a4ea
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-07 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 12:25 [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event Douglas RAILLARD
2023-03-06 12:51 ` Mukesh Ojha
2023-03-06 16:15 ` Steven Rostedt
2023-03-06 17:25 ` Steven Rostedt
2023-03-07 6:01 ` Chao Yu
2023-03-07 17:40 ` patchwork-bot+f2fs [this message]
2023-03-28 23:03 ` [f2fs-dev] " Steven Rostedt
2023-03-29 0:36 ` Jaegeuk Kim
2023-03-29 1:01 ` Steven Rostedt
2023-03-29 17:41 ` Linus Torvalds
2023-08-14 13:32 ` Kajetan Puchalski
2023-08-14 14:39 ` Kajetan Puchalski
2023-08-14 20:37 ` Jaegeuk Kim
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=167821082479.1693.18260840022075703789.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=douglas.raillard@arm.com \
--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=mhiramat@kernel.org \
--cc=rostedt@goodmis.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