[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240320190925.eb67348ecd08ed73d58cdc2d@kernel.org>
Date: Wed, 20 Mar 2024 19:09:25 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Ye Bin <yebin10@...wei.com>
Cc: <rostedt@...dmis.org>, <mathieu.desnoyers@...icios.com>,
<linux-trace-kernel@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 5/8] tracing: add new type "%pd/%pD" in readme_msg[]
Hi Ye,
Can you split this into
(1)
> - "\t symstr, <type>\\[<array-size>\\]\n"
> + "\t symstr, %pd, <type>\\[<array-size>\\]\n"
and
(2)
> - "\t symstr, %pd, <type>\\[<array-size>\\]\n"
> + "\t symstr, %pd/%pD, <type>\\[<array-size>\\]\n"
And merge (1) into [PATCH 3/8], (2) into [PATCH 5/8], so that
the feature patch itself updates the readme text?
This is because even if one of the patch drops, others can
show its feature on readme.
Thank you,
On Fri, 15 Mar 2024 14:55:37 +0800
Ye Bin <yebin10@...wei.com> wrote:
> Signed-off-by: Ye Bin <yebin10@...wei.com>
> ---
> kernel/trace/trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index b12f8384a36a..831dfd0773a4 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -5510,7 +5510,7 @@ static const char readme_msg[] =
> "\t +|-[u]<offset>(<fetcharg>), \\imm-value, \\\"imm-string\"\n"
> "\t type: s8/16/32/64, u8/16/32/64, x8/16/32/64, char, string, symbol,\n"
> "\t b<bit-width>@<bit-offset>/<container-size>, ustring,\n"
> - "\t symstr, <type>\\[<array-size>\\]\n"
> + "\t symstr, %pd/%pD, <type>\\[<array-size>\\]\n"
> #ifdef CONFIG_HIST_TRIGGERS
> "\t field: <stype> <name>;\n"
> "\t stype: u8/u16/u32/u64, s8/s16/s32/s64, pid_t,\n"
> --
> 2.31.1
>
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists