From: Cao Ruichuang <create0818@163.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2] trace-cmd report: Add spacing before raw data flags
Date: Tue, 7 Apr 2026 00:53:33 +0800 [thread overview]
Message-ID: <20260406165333.46051-1-create0818@163.com> (raw)
In-Reply-To: <20260406153221.33256-1-create0818@163.com>
In raw report mode, the CPU field is followed immediately by the
raw data flags. Without a separator, the flags get glued to the
closing CPU bracket and the output becomes hard to parse visually.
Add a leading space before the raw flag field so the raw report
output keeps the same field separation that the non-raw path already
has.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=221303
Signed-off-by: Cao Ruichuang <create0818@163.com>
---
tracecmd/trace-read.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tracecmd/trace-read.c b/tracecmd/trace-read.c
index 355ee0f4..962ebd89 100644
--- a/tracecmd/trace-read.c
+++ b/tracecmd/trace-read.c
@@ -871,7 +871,7 @@ void trace_show_data(struct tracecmd_input *handle, struct tep_record *record)
TEP_PRINT_CPU);
if (raw_format)
- trace_seq_printf(&s, "-0x%x",
+ trace_seq_printf(&s, " -0x%x",
tep_data_flags(pevent, record));
else
tep_print_event(pevent, &s, record,
--
2.39.5 (Apple Git-154)
prev parent reply other threads:[~2026-04-06 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 15:32 [PATCH] trace-cmd report: add spacing before raw data flags CaoRuichuang
2026-04-06 16:36 ` Steven Rostedt
2026-04-06 16:53 ` Cao Ruichuang [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=20260406165333.46051-1-create0818@163.com \
--to=create0818@163.com \
--cc=linux-trace-devel@vger.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