From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sandipan Das <sandipan@linux.ibm.com>,
Colin Ian King <colin.i.king@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf vendor events powerpc: Fix spelling mistake "fpr" -> "for"
Date: Mon, 12 Dec 2022 12:40:42 -0300 [thread overview]
Message-ID: <Y5dLer9nOR6j0Xmb@kernel.org> (raw)
In-Reply-To: <20221207135645.2327224-1-colin.i.king@gmail.com>
Em Wed, Dec 07, 2022 at 01:56:45PM +0000, Colin Ian King escreveu:
> There is a spelling mistake in the description text. Fix it.
Sandipan,
Is this generated from some other file? Or can I apply this one?
- Arnaldo
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> tools/perf/pmu-events/arch/powerpc/power8/other.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/pmu-events/arch/powerpc/power8/other.json b/tools/perf/pmu-events/arch/powerpc/power8/other.json
> index f1f2965f6775..6de8c472ec99 100644
> --- a/tools/perf/pmu-events/arch/powerpc/power8/other.json
> +++ b/tools/perf/pmu-events/arch/powerpc/power8/other.json
> @@ -2996,7 +2996,7 @@
> {
> "EventCode": "0x308e",
> "EventName": "PM_SWAP_COMPLETE_GPR",
> - "BriefDescription": "swap cast in completed fpr gpr",
> + "BriefDescription": "swap cast in completed for gpr",
> "PublicDescription": ""
> },
> {
> --
> 2.38.1
--
- Arnaldo
prev parent reply other threads:[~2022-12-12 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 13:56 [PATCH] perf vendor events powerpc: Fix spelling mistake "fpr" -> "for" Colin Ian King
2022-12-12 15:40 ` 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=Y5dLer9nOR6j0Xmb@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).