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 3/3] perf vendor events amd: Fix a misspelling in the amdzen3 table
Date: Fri, 20 Nov 2026 18:00:54 +0000	[thread overview]
Message-ID: <sashiko-outbox-225775@kernel.org> (raw)
In-Reply-To: <20261120175840.1274637-4-takano32@gmail.com>

> One word is misspelled in the amdzen3 branch table: "Instrcution" instead
> of "Instruction" in the BriefDescription of bp_l1_tlb_fetch_hit.if4k, so
> `perf list` prints the misspelling as it is.
> 
> Only the description changes.  Regenerating the tables with
> 
>   jevents.py x86 all tools/perf/pmu-events/arch out.c out-str.c
> 
> leaves the generated table and the string table identical except for that
> one word: every event name and event code is untouched, and the string
> table does not change size.
> 
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>

Sashiko has reviewed this patch and found no issues.

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


      reply	other threads:[~2026-11-20 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 17:58 [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions TAKANO Mitsuhiro
2026-11-20 17:58 ` [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables TAKANO Mitsuhiro
2026-11-20 18:01   ` sashiko-bot
2026-11-20 17:58 ` [PATCH 2/3] perf vendor events intel: Fix misspellings in the Intel model tables TAKANO Mitsuhiro
2026-11-20 18:01   ` sashiko-bot
2026-11-20 17:58 ` [PATCH 3/3] perf vendor events amd: Fix a misspelling in the amdzen3 table TAKANO Mitsuhiro
2026-11-20 18:00   ` 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=sashiko-outbox-225775@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