From: Steven Rostedt <rostedt@goodmis.org>
To: Oscar Shiang <oscar0225@livemail.tw>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix inconsistent style of mini-HOWTO
Date: Wed, 16 Feb 2022 11:55:06 -0500 [thread overview]
Message-ID: <20220216115506.790ee23e@gandalf.local.home> (raw)
In-Reply-To: <TYCP286MB19130AA4A9C6FC5A8793DED2A1359@TYCP286MB1913.JPNP286.PROD.OUTLOOK.COM>
On Thu, 17 Feb 2022 00:50:06 +0800
Oscar Shiang <oscar0225@livemail.tw> wrote:
> Each description should start with a hyphen and a space. Insert
> spaces to fix it.
>
I can take this, but there's a possibility that it will be reverted. The
output of the README in the tracefs file is an API. That is, the content of
the text is used to determine what version and what options of tracing is
enabled.
If something is scanning for the trace_clock or timestamp_mode lines, doing
an exact match of the entire context, this could break that code. If
there's any report of that happening (and we should look for anything that
might do that), then this will need to be reverted.
-- Steve
> Signed-off-by: Oscar Shiang <oscar0225@livemail.tw>
> ---
> kernel/trace/trace.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 7c2578efd..a0d10e949 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -5458,7 +5458,7 @@ static const char readme_msg[] =
> " error_log\t- error log for failed commands (that support it)\n"
> " buffer_size_kb\t- view and modify size of per cpu buffer\n"
> " buffer_total_size_kb - view total size of all cpu buffers\n\n"
> - " trace_clock\t\t-change the clock used to order events\n"
> + " trace_clock\t\t- change the clock used to order events\n"
> " local: Per cpu clock but may not be synced across CPUs\n"
> " global: Synced across CPUs but slows tracing down.\n"
> " counter: Not a clock, but just an increment\n"
> @@ -5467,7 +5467,7 @@ static const char readme_msg[] =
> #ifdef CONFIG_X86_64
> " x86-tsc: TSC cycle counter\n"
> #endif
> - "\n timestamp_mode\t-view the mode used to timestamp events\n"
> + "\n timestamp_mode\t- view the mode used to timestamp events\n"
> " delta: Delta difference against a buffer-wide timestamp\n"
> " absolute: Absolute (standalone) timestamp\n"
> "\n trace_marker\t\t- Writes into this file writes into the kernel buffer\n"
> --
> 2.25.1
prev parent reply other threads:[~2022-02-16 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:50 Oscar Shiang
2022-02-16 16:55 ` Steven Rostedt [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=20220216115506.790ee23e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oscar0225@livemail.tw \
/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
all inboxes | Powered by JetHome®