From: Nikita Shubin <nikita.shubin@maquefel.me>
To: eric.lin@sifive.com
Cc: acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, aou@eecs.berkeley.edu,
dminus@andestech.com, inochiama@outlook.com, irogers@google.com,
jisheng.teoh@starfivetech.com, jolsa@kernel.org,
kan.liang@linux.intel.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org,
linux-riscv@lists.infradead.org, locus84@andestech.com,
mark.rutland@arm.com, mingo@redhat.com, n.shubin@yadro.com,
namhyung@kernel.org, palmer@dabbelt.com, peterlin@andestech.com,
peterz@infradead.org, samuel.holland@sifive.com
Subject: Re: [PATCH] perf arch events: Fix duplicate RISC-V SBI firmware event name
Date: Fri, 19 Jul 2024 11:51:06 +0300 [thread overview]
Message-ID: <12bd744ea481c8a3505e6f4869d409d24d3db795.camel@maquefel.me> (raw)
In-Reply-To: <20240718152254.16007-1-eric.lin@sifive.com>
Hi Eric,
Nice catch!
Shouldn't it fix every patch that copied affected 'firmware.json' by
the way ?
Something like:
Fixes: 8f0dcb4e7364 ("perf arch events: riscv sbi firmware std event
files")
Fixes: c4f769d4093d ("perf vendor events riscv: add Sifive U74 JSON
file")
Fixes: acbf6de674ef ("perf vendor events riscv: Add StarFive Dubhe-80
JSON file")
Fixes: 7340c6df49df ("perf vendor events riscv: add T-HEAD C9xx JSON
file")
Fixes: f5102e31c209 ("riscv: andes: Support specifying symbolic
firmware and hardware raw event")
Reviewed-by: Nikita Shubin <n.shubin@yadro.com>
next prev parent reply other threads:[~2024-07-19 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 15:22 [PATCH] perf arch events: Fix duplicate RISC-V SBI firmware event name Eric Lin
2024-07-19 8:51 ` Nikita Shubin [this message]
2024-07-19 9:37 ` Eric Lin
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=12bd744ea481c8a3505e6f4869d409d24d3db795.camel@maquefel.me \
--to=nikita.shubin@maquefel.me \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=dminus@andestech.com \
--cc=eric.lin@sifive.com \
--cc=inochiama@outlook.com \
--cc=irogers@google.com \
--cc=jisheng.teoh@starfivetech.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=locus84@andestech.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=n.shubin@yadro.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterlin@andestech.com \
--cc=peterz@infradead.org \
--cc=samuel.holland@sifive.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).