From: sashiko-bot@kernel.org
To: "Manuel Ebner" <manuelebnerli@mailbox.org>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: trace: histogram-design: fix bracket, improve wording
Date: Thu, 03 Sep 2026 07:15:20 +0000 [thread overview]
Message-ID: <20260903071520.BA5121F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260903070249.713483-2-manuelebnerli@mailbox.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The patch fails to implement the missing parenthesis fix claimed in the commit message.
- [Low] An unrelated line of documentation was accidentally deleted, breaking a sentence structure.
--
commit 708a883b89775bdba5b9179959e1d7aeeadf6600
Author: Manuel Ebner <manuelebnerli@mailbox.org>
Documentation: trace: histogram-design: fix bracket, improve wording
This commit aims to add a missing parenthesis and include a note about the
new way of triggering an event in the histogram-design documentation.
> ---
> @ Steven, I added this line, because else the references wouldn't make sense.
> References: $wakeup_lat, next_pid
>
> + ... (which
> +could equivalently be written trace(wakeup_latency,$wakeup_lat,next_pid)
> are implemented, the parameters specified to the trace handler must be
> variables. In this case, $wakeup_lat is obviously a variable, but
> next_pid isn't, since it's just naming a field in the sched_switch
> ---
[Severity: Medium]
It looks like the intended fix for the missing parenthesis was accidentally
placed between the `---` separators in the commit message. As a result, this
hunk is treated as commentary by git and dropped during patch application,
so the parenthesis fix is missing from the actual file. Should this hunk be
moved into the diff proper?
> diff --git a/Documentation/trace/histogram-design.rst b/Documentation/trace/histogram-design.rst
> index 41a726cd35369..86c83b177e446 100644
> --- a/Documentation/trace/histogram-design.rst
> +++ b/Documentation/trace/histogram-design.rst
> @@ -25,7 +25,7 @@ tracing_map.c.
>
> If the kernel is compiled with CONFIG_HIST_TRIGGERS_DEBUG set, an
> event file named 'hist_debug' will appear in each event's
> -subdirectory. This file can be read at any time and will display some
> +
[Severity: Low]
Was this deletion intentional? It appears an unrelated line of documentation
was accidentally removed here, breaking the sentence structure of the
paragraph.
> of the hist trigger internals described in this document. Specific
> examples and output will be described in test cases below.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260903070249.713483-2-manuelebnerli@mailbox.org?part=1
prev parent reply other threads:[~2026-09-03 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 7:02 [PATCH v2] Documentation: trace: histogram-design: fix bracket, improve wording Manuel Ebner
2026-09-03 7:11 ` Manuel Ebner
2026-09-03 18:14 ` Steven Rostedt
2026-09-03 7:15 ` sashiko-bot [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=20260903071520.BA5121F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=sashiko-reviews@lists.linux.dev \
/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