From: Diederik de Haas <didi.debian@cknow.org>
To: Edward <edward.baker@intel.com>, Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Kan Liang <kan.liang@linux.intel.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Sandipan Das <sandipan.das@amd.com>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-perf-users@vger.kernel.org>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@vger.kernel.org>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] tools/perf: Various spelling fixes
Date: Sat, 21 Jan 2023 21:53:51 +0100 [thread overview]
Message-ID: <3632669.kckeHSHuci@prancing-pony> (raw)
In-Reply-To: <CAP-5=fX1-3ZnXk8G2fB0q9F3MjjA+zWWm1LbuYGc5nL5v3bXYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Saturday, 21 January 2023 20:25:46 CET Ian Rogers wrote:
> The JSON files are generated from Intel information here:
> https://github.com/intel/perfmon/
> Fixing the spelling in the tree means that when we update the
> incorrect spelling will be generated again. Intel are looking at the
> matter, I've added Edward Baker to the e-mail. To make it clearer,
> could you separate the JSON fixes from the tool fixes?
Yes, I'll send a v2 patch with the JSON files excluded.
And I'll send a PR to the GH repo.
> Could you also add the mistakes found by this list to:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scri
> pts/spelling.txt which will mean the checkpatch.pl tool will flag the
> mistakes should regressions happen.
Ha! That's based on Debian's lintian tool (too) :-D
I'll make/send a separate patch to include the ones lintian found.
Lintian found several more, but I filtered the list I send to belong to `tools/
perf` hoping/assuming the To list wouldn't be so long (which didn't work out
as well as I hoped ;-)).
> Beside those 2 suggestions, the corrections look great and thank you
> for taking the time to do this.
Cool :-)
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Diederik de Haas <didi.debian@cknow.org>
To: Edward <edward.baker@intel.com>, Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Kan Liang <kan.liang@linux.intel.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Sandipan Das <sandipan.das@amd.com>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-perf-users@vger.kernel.org>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@vger.kernel.org>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] tools/perf: Various spelling fixes
Date: Sat, 21 Jan 2023 21:53:51 +0100 [thread overview]
Message-ID: <3632669.kckeHSHuci@prancing-pony> (raw)
In-Reply-To: <CAP-5=fX1-3ZnXk8G2fB0q9F3MjjA+zWWm1LbuYGc5nL5v3bXYg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]
On Saturday, 21 January 2023 20:25:46 CET Ian Rogers wrote:
> The JSON files are generated from Intel information here:
> https://github.com/intel/perfmon/
> Fixing the spelling in the tree means that when we update the
> incorrect spelling will be generated again. Intel are looking at the
> matter, I've added Edward Baker to the e-mail. To make it clearer,
> could you separate the JSON fixes from the tool fixes?
Yes, I'll send a v2 patch with the JSON files excluded.
And I'll send a PR to the GH repo.
> Could you also add the mistakes found by this list to:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scri
> pts/spelling.txt which will mean the checkpatch.pl tool will flag the
> mistakes should regressions happen.
Ha! That's based on Debian's lintian tool (too) :-D
I'll make/send a separate patch to include the ones lintian found.
Lintian found several more, but I filtered the list I send to belong to `tools/
perf` hoping/assuming the To list wouldn't be so long (which didn't work out
as well as I hoped ;-)).
> Beside those 2 suggestions, the corrections look great and thank you
> for taking the time to do this.
Cool :-)
Cheers,
Diederik
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-21 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 18:46 [PATCH] tools/perf: Various spelling fixes Diederik de Haas
2023-01-21 19:25 ` Ian Rogers
2023-01-21 20:53 ` Diederik de Haas [this message]
2023-01-21 20:53 ` Diederik de Haas
2023-01-22 12:37 ` Diederik de Haas
2023-01-23 13:10 ` Arnaldo Carvalho de Melo
2023-01-23 17:24 ` Ian Rogers
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=3632669.kckeHSHuci@prancing-pony \
--to=didi.debian@cknow.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=edward.baker@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=zhengjun.xing@linux.intel.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.