From: John Garry <john.garry@huawei.com>
To: "nakamura.shun@fujitsu.com" <nakamura.shun@fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxarm@openeuler.org" <linuxarm@openeuler.org>,
"james.clark@arm.com" <james.clark@arm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@redhat.com" <jolsa@redhat.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"irogers@google.com" <irogers@google.com>,
"kjain@linux.ibm.com" <kjain@linux.ibm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/4] perf vendor events arm64: Add common and uarch event JSON
Date: Thu, 28 Jan 2021 08:41:57 +0000 [thread overview]
Message-ID: <a668afcc-b06b-04d3-aba2-507a8d1d8f6e@huawei.com> (raw)
In-Reply-To: <OSBPR01MB460053B9A7E7A1710D73D21EF7BA9@OSBPR01MB4600.jpnprd01.prod.outlook.com>
On 28/01/2021 05:30, nakamura.shun@fujitsu.com wrote:
> Hi ,john
>
> I would like to make a comment because there is excess or deficiency in comma.
> There are no differences in pmu-events.c.
>
>> + {
>> + "PublicDescription": "Attributable Bus access",
>> + "EventCode": "0x19",
>> + "EventName": "BUS_ACCESS",
>> + "BriefDescription": "Attributable Bus access",
>> + },
> Comma is not required at the end of BriefDescription.
>
>> + {
>> + "PublicDescription": "Bus cycle"
>> + "EventCode": "0x1D",
>> + "EventName": "BUS_CYCLES",
>> + "BriefDescription": "Bus cycle"
>> + },
> Missing comma at end of PublicDescription.
>
>> + {
>> + "PublicDescription": "Attributable Last level cache memory read"
>> + "EventCode": "0x36",
>> + "EventName": "LL_CACHE_RD",
>> + "BriefDescription": "Attributable Last level cache memory read"
>> + },
>> + {
>> + "PublicDescription": "Last level cache miss, read"
>> + "EventCode": "0x37",
>> + "EventName": "LL_CACHE_MISS_RD",
>> + "BriefDescription": "Last level cache miss, read"
>> + },
> Missing comma at end of PublicDescription.
>
>> + },
>> +]
> Commas are not required.
>
> Best Regards
> Shunsuke
Fine, I can fix those up and re-post today.
Thanks,
john
next prev parent reply other threads:[~2021-01-28 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:53 [PATCH 0/4] perf vendor events arm64: Some tidy-up/refactoring John Garry
2021-01-25 11:53 ` [PATCH 1/4] perf vendor events arm64: Fix Ampere eMag event typo John Garry
2021-01-25 11:53 ` [PATCH 2/4] perf vendor events arm64: Add common and uarch event JSON John Garry
2021-01-28 5:30 ` nakamura.shun
2021-01-28 8:41 ` John Garry [this message]
2021-01-25 11:53 ` [PATCH 3/4] perf vendor events arm64: Reference common and uarch events for Ampere eMag John Garry
2021-01-25 11:53 ` [PATCH 4/4] perf vendor events arm64: Reference common and uarch events for A76 John Garry
2021-01-25 12:49 ` [PATCH 0/4] perf vendor events arm64: Some tidy-up/refactoring John Garry
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=a668afcc-b06b-04d3-aba2-507a8d1d8f6e@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=nakamura.shun@fujitsu.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®