From: patchwork-bot+linux-riscv@kernel.org
To: Eric Lin <eric.lin@sifive.com>
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, palmer@dabbelt.com, aou@eecs.berkeley.edu,
peterlin@andestech.com, dminus@andestech.com,
locus84@andestech.com, jisheng.teoh@starfivetech.com,
inochiama@outlook.com, n.shubin@yadro.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
samuel.holland@sifive.com
Subject: Re: [PATCH v2] perf arch events: Fix duplicate RISC-V SBI firmware event name
Date: Thu, 01 Aug 2024 16:40:37 +0000 [thread overview]
Message-ID: <172253043753.13740.1828763400860823722.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240719115018.27356-1-eric.lin@sifive.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 19 Jul 2024 19:50:18 +0800 you wrote:
> Currently, the RISC-V firmware JSON file has duplicate event name
> "FW_SFENCE_VMA_RECEIVED". According to the RISC-V SBI PMU extension[1],
> the event name should be "FW_SFENCE_VMA_ASID_SENT".
>
> Before this patch:
> $ perf list
>
> [...]
Here is the summary with links:
- [v2] perf arch events: Fix duplicate RISC-V SBI firmware event name
https://git.kernel.org/riscv/c/63ba5b0fb4f5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-01 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 11:50 [PATCH v2] perf arch events: Fix duplicate RISC-V SBI firmware event name Eric Lin
2024-07-19 12:22 ` Inochi Amaoto
2024-07-19 15:21 ` Andrew Jones
2024-07-29 18:12 ` [v2] " Atish Patra
2024-07-29 18:19 ` Atish Patra
2024-08-01 15:26 ` Ian Rogers
2024-08-01 16:40 ` patchwork-bot+linux-riscv [this message]
2024-08-01 17:04 ` [PATCH v2] " 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=172253043753.13740.1828763400860823722.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=acme@kernel.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=locus84@andestech.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