Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "TAKANO Mitsuhiro" <takano32@gmail.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf vendor events arm64: AmpereOne/AmpereOneX: Fix typos
Date: Sat, 07 Nov 2026 05:19:44 +0000	[thread overview]
Message-ID: <sashiko-outbox-202609@kernel.org> (raw)
In-Reply-To: <20261107051730.1880691-1-takano32@gmail.com>

> Three distinct words are misspelled in eight description fields in the
> AmpereOne and AmpereOneX PMU tables: "Preditable" in BPU_BTB_UPDATE
> (AmpereOneX only), "satisified" in LD_FROM_ST_FWD, and "misprediciton"
> in the branch_mispredict metric.  jevents.py copies the strings into the
> generated tables, so perf list prints them and a grep for the correct
> spelling misses the entries.
> 
> Fix both fields where an entry has them; the metrics entries carry only a
> brief description.  No event code, metric expression or reported value
> changes, and the generated tables are not tracked, so the diff is JSON
> only.  ISTALL - the other codespell hit here - is the ETM stall-control
> bit name, left alone.
> 
> Written with Hermes Agent, an LLM assistant.  Running jevents.py on this
> change produces none of the three words; perf was not rebuilt, so the
> perf list output was not checked.
> 
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261107051730.1880691-1-takano32@gmail.com?part=1


  reply	other threads:[~2026-11-07  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  5:17 [PATCH] perf vendor events arm64: AmpereOne/AmpereOneX: Fix typos TAKANO Mitsuhiro
2026-11-07  5:19 ` sashiko-bot [this message]
2026-11-11 19:09 ` Namhyung Kim

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=sashiko-outbox-202609@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=takano32@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