All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Douglas RAILLARD <douglas.raillard@arm.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	"open list:F2FS FILE SYSTEM"
	<linux-f2fs-devel@lists.sourceforge.net>,
	"open list:TRACING" <linux-kernel@vger.kernel.org>,
	"open list:TRACING" <linux-trace-kernel@vger.kernel.org>
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event
Date: Tue, 7 Mar 2023 14:01:36 +0800	[thread overview]
Message-ID: <fa4cfb68-5866-ecea-4073-4c5c52e587c9@kernel.org> (raw)
In-Reply-To: <20230306122549.236561-1-douglas.raillard@arm.com>

On 2023/3/6 20:25, Douglas RAILLARD 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;
> 
> Instead of 12:
> 
>          field:nid_t nid[3];     offset:24;      size:12;        signed:0;
> 
> This also fixes the reported offset of subsequent fields so that they
> match with the actual struct layout.
> 
> 
> Signed-off-by: Douglas Raillard <douglas.raillard@arm.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

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Douglas RAILLARD <douglas.raillard@arm.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	"open list:F2FS FILE SYSTEM"
	<linux-f2fs-devel@lists.sourceforge.net>,
	"open list:TRACING" <linux-kernel@vger.kernel.org>,
	"open list:TRACING" <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event
Date: Tue, 7 Mar 2023 14:01:36 +0800	[thread overview]
Message-ID: <fa4cfb68-5866-ecea-4073-4c5c52e587c9@kernel.org> (raw)
In-Reply-To: <20230306122549.236561-1-douglas.raillard@arm.com>

On 2023/3/6 20:25, Douglas RAILLARD 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;
> 
> Instead of 12:
> 
>          field:nid_t nid[3];     offset:24;      size:12;        signed:0;
> 
> This also fixes the reported offset of subsequent fields so that they
> match with the actual struct layout.
> 
> 
> Signed-off-by: Douglas Raillard <douglas.raillard@arm.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  parent reply	other threads:[~2023-03-07  6:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 12:25 [f2fs-dev] [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event Douglas RAILLARD
2023-03-06 12:25 ` Douglas RAILLARD
2023-03-06 12:51 ` [f2fs-dev] " Mukesh Ojha
2023-03-06 12:51   ` Mukesh Ojha
2023-03-06 16:15 ` [f2fs-dev] " Steven Rostedt
2023-03-06 16:15   ` Steven Rostedt
2023-03-06 17:25   ` [f2fs-dev] " Steven Rostedt
2023-03-06 17:25     ` Steven Rostedt
2023-03-07  6:01 ` Chao Yu [this message]
2023-03-07  6:01   ` Chao Yu
2023-03-07 17:40 ` [f2fs-dev] " patchwork-bot+f2fs
2023-03-07 17:40   ` patchwork-bot+f2fs
2023-03-28 23:03   ` Steven Rostedt
2023-03-28 23:03     ` Steven Rostedt
2023-03-29  0:36     ` Jaegeuk Kim
2023-03-29  0:36       ` Jaegeuk Kim
2023-03-29  1:01       ` Steven Rostedt
2023-03-29  1:01         ` Steven Rostedt
2023-03-29 17:41       ` Linus Torvalds
2023-03-29 17:41         ` Linus Torvalds
2023-08-14 13:32 ` Kajetan Puchalski
2023-08-14 13:32   ` Kajetan Puchalski
2023-08-14 14:39   ` [f2fs-dev] " Kajetan Puchalski
2023-08-14 14:39     ` Kajetan Puchalski
2023-08-14 20:37     ` [f2fs-dev] " Jaegeuk Kim
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=fa4cfb68-5866-ecea-4073-4c5c52e587c9@kernel.org \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.