From: sashiko-bot@kernel.org
To: "TAKANO Mitsuhiro" <takano32@gmail.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf vendor events arm64: Fix typos in event descriptions
Date: Sun, 08 Nov 2026 18:49:30 +0000 [thread overview]
Message-ID: <sashiko-outbox-203914@kernel.org> (raw)
In-Reply-To: <20261108184654.3811267-1-takano32@gmail.com>
> Six entries in common-and-microarch.json spell Statistical as "Statisical"
> (the SAMPLE_FEED_* events), and one entry in the Fujitsu a64fx table, the
> L2HWPF_STREAM_PF event, spells prefetcher as "prefecher" in both its
> BriefDescription and its PublicDescription.
>
> The SAMPLE_FEED_* events are inherited through ArchStdEvent by the
> neoverse-n3, neoverse-v3 and t410 tables, so the misspelling reaches those
> three generated tables. The a64fx pair appears once, because the long
> description is dropped when it equals the brief one.
>
> Spell the words correctly. Event names, codes and expressions are
> unchanged.
>
> Written with Hermes Agent, an LLM assistant. Running jevents.py for arm64
> before and after this change removes 12 occurrences of "Statisical" and the
> one "prefecher" from the generated string table; perf was not rebuilt.
>
> Fixes: 994256a79867 ("perf vendor events arm64: Add N3 events/metrics")
> Fixes: 5497b23e870c ("perf vendor events arm64: Add Fujitsu A64FX pmu event")
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108184654.3811267-1-takano32@gmail.com?part=1
next prev parent reply other threads:[~2026-11-08 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 18:46 [PATCH] perf vendor events arm64: Fix typos in event descriptions TAKANO Mitsuhiro
2026-11-08 18:49 ` sashiko-bot [this message]
2026-11-09 10:20 ` James Clark
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-203914@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.