From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
Masanari Iida <standby24x7@gmail.com>
Cc: ak@linux.intel.com, kan.liang@intel.com,
linux-kernel@vger.kernel.org, acme@kernel.org,
Jin Yao <yao.jin@linux.intel.com>
Subject: Re: [PATCH] perf vendor events intel: Fix typos in floating-point.json
Date: Wed, 26 Jun 2019 10:54:53 -0400 [thread overview]
Message-ID: <fb1f9673-6b6a-e5c8-2ff4-945a59f1d919@linux.intel.com> (raw)
In-Reply-To: <20190626134746.GA2227@redhat.com>
On 6/26/2019 9:47 AM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jun 26, 2019 at 08:04:36PM +0900, Masanari Iida escreveu:
>> This patch fix some spelling typo in x86/*/floating-point.json
>
> These are auto-generated files, glad that you CCed your fixes to the
> Intel folks, hopefully they will in turn send it internally so that next
Yes, I have already fw the fixes to the internal team.
Once they update the database and release a new version, we will
generate a new patch.
Thanks,
Kan
> time we get an update with the fixes, ok?
>
> Thanks,
>
> - Arnaldo
>
>> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
>> ---
>> tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json | 2 +-
>> tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json | 2 +-
>> .../perf/pmu-events/arch/x86/westmereep-dp/floating-point.json | 2 +-
>> .../perf/pmu-events/arch/x86/westmereep-sp/floating-point.json | 2 +-
>> tools/perf/pmu-events/arch/x86/westmereex/floating-point.json | 2 +-
>> 5 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json b/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json
>> index 7d2f71a9dee3..6b9b9fe74f3b 100644
>> --- a/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json
>> +++ b/tools/perf/pmu-events/arch/x86/nehalemep/floating-point.json
>> @@ -15,7 +15,7 @@
>> "UMask": "0x4",
>> "EventName": "FP_ASSIST.INPUT",
>> "SampleAfterValue": "20000",
>> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)"
>> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)"
>> },
>> {
>> "PEBS": "1",
>> diff --git a/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json b/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json
>> index 7d2f71a9dee3..6b9b9fe74f3b 100644
>> --- a/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json
>> +++ b/tools/perf/pmu-events/arch/x86/nehalemex/floating-point.json
>> @@ -15,7 +15,7 @@
>> "UMask": "0x4",
>> "EventName": "FP_ASSIST.INPUT",
>> "SampleAfterValue": "20000",
>> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)"
>> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)"
>> },
>> {
>> "PEBS": "1",
>> diff --git a/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json
>> index 7d2f71a9dee3..6b9b9fe74f3b 100644
>> --- a/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json
>> +++ b/tools/perf/pmu-events/arch/x86/westmereep-dp/floating-point.json
>> @@ -15,7 +15,7 @@
>> "UMask": "0x4",
>> "EventName": "FP_ASSIST.INPUT",
>> "SampleAfterValue": "20000",
>> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)"
>> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)"
>> },
>> {
>> "PEBS": "1",
>> diff --git a/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json
>> index 7d2f71a9dee3..6b9b9fe74f3b 100644
>> --- a/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json
>> +++ b/tools/perf/pmu-events/arch/x86/westmereep-sp/floating-point.json
>> @@ -15,7 +15,7 @@
>> "UMask": "0x4",
>> "EventName": "FP_ASSIST.INPUT",
>> "SampleAfterValue": "20000",
>> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)"
>> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)"
>> },
>> {
>> "PEBS": "1",
>> diff --git a/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json b/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
>> index 7d2f71a9dee3..6b9b9fe74f3b 100644
>> --- a/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
>> +++ b/tools/perf/pmu-events/arch/x86/westmereex/floating-point.json
>> @@ -15,7 +15,7 @@
>> "UMask": "0x4",
>> "EventName": "FP_ASSIST.INPUT",
>> "SampleAfterValue": "20000",
>> - "BriefDescription": "X87 Floating poiint assists for invalid input value (Precise Event)"
>> + "BriefDescription": "X87 Floating point assists for invalid input value (Precise Event)"
>> },
>> {
>> "PEBS": "1",
>> --
>> 2.22.0.214.g8dca754b1e87
prev parent reply other threads:[~2019-06-26 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 11:04 [PATCH] perf vendor events intel: Fix typos in floating-point.json Masanari Iida
2019-06-26 13:47 ` Arnaldo Carvalho de Melo
2019-06-26 14:54 ` Liang, Kan [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=fb1f9673-6b6a-e5c8-2ff4-945a59f1d919@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=yao.jin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox