From: Steven Rostedt <rostedt@goodmis.org>
To: Ryan Chung <seokwoo.chung130@gmail.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] trace: minor documentation fixes for clarity and
Date: Tue, 2 Sep 2025 10:28:31 -0400 [thread overview]
Message-ID: <20250902102831.134a26c1@batman.local.home> (raw)
In-Reply-To: <20250831101736.11519-1-seokwoo.chung130@gmail.com>
On Sun, 31 Aug 2025 19:17:27 +0900
Ryan Chung <seokwoo.chung130@gmail.com> wrote:
> Resend: fixed recipients; no changes
>
> Hi all,
>
> This short series cleans up two small wording issues in the tracing docs to
> improve readability. There are no functional changes.
>
> Ryan Chung (2):
> trace: rephrase for clearer documentation
> trace: fix grammar error in debugging.rst
>
> Documentation/trace/boottime-trace.rst | 2 +-
> Documentation/trace/debugging.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
The only comments I would make is the subject tag for the trace files
is actually "tracing:" and not "trace:".
Also, even though the changes are minor, a simple change log would
still be nice.
-- Steve
next prev parent reply other threads:[~2025-09-02 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 10:17 [PATCH 0/2] trace: minor documentation fixes for clarity and Ryan Chung
2025-08-31 10:17 ` [PATCH 1/2] trace: rephrase for clearer documentation Ryan Chung
2025-08-31 10:17 ` [PATCH 2/2] trace: fix grammar error in debugging.rst Ryan Chung
2025-09-02 14:28 ` Steven Rostedt [this message]
2025-09-03 18:25 ` [PATCH 0/2] trace: minor documentation fixes for clarity and Ryan Chung
2025-09-03 19:52 ` Steven Rostedt
2025-09-03 21:32 ` Jonathan Corbet
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=20250902102831.134a26c1@batman.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=seokwoo.chung130@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).