Linux Trace Kernel
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Tracing <linux-trace-kernel@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Tom Zanussi <zanussi@kernel.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v2 0/5] Histogram docs formatting cleanup
Date: Thu, 18 Sep 2025 10:38:56 -0600	[thread overview]
Message-ID: <871po390m7.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250916054202.582074-2-bagasdotme@gmail.com>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> Hi,
>
> Here's a formatting assortment for trace histogram docs. The shortlog
> below should be self-explanatory.
>
> Enjoy!
>
> Changes since v1 [1]:
>
>   * Apply review tags (Masami, Tom)
>   * Reword patch description for ftrace cross-reference link (Masami, [5/5])
>
> [1]: https://lore.kernel.org/linux-doc/20250911042527.22573-1-bagasdotme@gmail.com/
>
> Bagas Sanjaya (5):
>   Documentation: trace: histogram: Fix histogram trigger subsection
>     number order
>   Documentation: trace: histogram-design: Trim trailing vertices in
>     diagram explanation text
>   Documentation: trace: historgram-design: Separate sched_waking
>     histogram section heading and the following diagram
>   Documentation: trace: histogram-design: Wrap introductory note in
>     note:: directive
>   Documentation: trace: histogram: Convert ftrace docs cross-reference
>
>  Documentation/trace/histogram-design.rst | 151 ++++++++++++-----------
>  Documentation/trace/histogram.rst        |  38 +++---
>  2 files changed, 96 insertions(+), 93 deletions(-)

Steve, will you pick these up, or should I grab them?

Thanks,

jon

  parent reply	other threads:[~2025-09-18 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  5:41 [PATCH v2 0/5] Histogram docs formatting cleanup Bagas Sanjaya
2025-09-16  5:41 ` [PATCH v2 1/5] Documentation: trace: histogram: Fix histogram trigger subsection number order Bagas Sanjaya
2025-09-16  5:42 ` [PATCH v2 2/5] Documentation: trace: histogram-design: Trim trailing vertices in diagram explanation text Bagas Sanjaya
2025-09-16  5:42 ` [PATCH v2 3/5] Documentation: trace: historgram-design: Separate sched_waking histogram section heading and the following diagram Bagas Sanjaya
2025-09-16  5:42 ` [PATCH v2 4/5] Documentation: trace: histogram-design: Wrap introductory note in note:: directive Bagas Sanjaya
2025-09-16  5:42 ` [PATCH v2 5/5] Documentation: trace: histogram: Convert ftrace docs cross-reference Bagas Sanjaya
2025-09-18 16:38 ` Jonathan Corbet [this message]
2025-09-18 17:05   ` [PATCH v2 0/5] Histogram docs formatting cleanup Steven Rostedt
2025-09-18 18:20     ` 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=871po390m7.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --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=rostedt@goodmis.org \
    --cc=zanussi@kernel.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