From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@linaro.org>
Cc: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Leo Yan <leo.yan@linux.dev>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>
Subject: Re: [PATCH v2 2/2] perf vendor events arm64 AmpereOne: Fix typos in metrics' descriptions
Date: Fri, 12 Sep 2025 15:27:40 -0300 [thread overview]
Message-ID: <aMRmHFNWjB74Bwy8@x1> (raw)
In-Reply-To: <fc2ee38c-b163-4b7e-9ba2-c2b93d0fc691@linaro.org>
On Thu, Sep 11, 2025 at 09:26:47AM +0100, James Clark wrote:
> On 10/09/2025 8:52 pm, Ilkka Koskinen wrote:
> > While fixing a typo in "l1d_cache_access_prefetches" in AmpereOneX,
> > a few other typos were found in metrics' descriptions too. While AmpereOne
> > doesn't have the metric, it did have the typos in the descriptions.
> >
> > Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
> Reviewed-by: James Clark <james.clark@linaro.org>
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2025-09-12 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 19:52 [PATCH v2 0/2] perf vendor events arm64 AmpereOneX/AmpereOne: Fix typo in l1d_cache_access_prefetches and a few typos in metrics descriptions Ilkka Koskinen
2025-09-10 19:52 ` [PATCH v2 1/2] perf vendor events arm64 AmpereOneX: Fix typo - should be l1d_cache_access_prefetches Ilkka Koskinen
2025-09-10 19:52 ` [PATCH v2 2/2] perf vendor events arm64 AmpereOne: Fix typos in metrics' descriptions Ilkka Koskinen
2025-09-11 8:26 ` James Clark
2025-09-12 18:27 ` Arnaldo Carvalho de Melo [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=aMRmHFNWjB74Bwy8@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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