From: patchwork-bot+linux-riscv@kernel.org
To: Vadim Shakirov <vadim.shakirov@syntacore.com>
Cc: linux-riscv@lists.infradead.org, atishp@atishpatra.org,
anup@brainfault.org, will@kernel.org, mark.rutland@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2,RESEND 0/2] drivers: perf: fix crash with the legacy riscv driver
Date: Wed, 28 Feb 2024 15:10:29 +0000 [thread overview]
Message-ID: <170913302975.9913.9405105778490456621.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227170002.188671-1-vadim.shakirov@syntacore.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 27 Feb 2024 20:00:00 +0300 you wrote:
> This series fix crash with the legacy riscv driver when configs:
> CONFIG_RISCV_PMU_LEGACY=y and CONFIG_RISCV_PMU_SBI=n and you try
> to perf record
>
> Vadim Shakirov (2):
> drivers: perf: added capabilities for legacy PMU
> drivers: perf: ctr_get_width function for legacy is not defined
>
> [...]
Here is the summary with links:
- [v2,RESEND,1/2] drivers: perf: added capabilities for legacy PMU
https://git.kernel.org/riscv/c/65730fe8f4fb
- [v2,RESEND,2/2] drivers: perf: ctr_get_width function for legacy is not defined
https://git.kernel.org/riscv/c/682dc133f83e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-02-28 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 17:00 [PATCH v2,RESEND 0/2] drivers: perf: fix crash with the legacy riscv driver Vadim Shakirov
2024-02-27 17:00 ` [PATCH v2,RESEND 1/2] drivers: perf: added capabilities for legacy PMU Vadim Shakirov
2024-02-27 19:26 ` Alexandre Ghiti
2024-02-27 19:38 ` Alexandre Ghiti
2024-02-27 20:56 ` Palmer Dabbelt
2024-02-27 17:00 ` [PATCH v2,RESEND 2/2] drivers: perf: ctr_get_width function for legacy is not defined Vadim Shakirov
2024-02-27 19:17 ` Alexandre Ghiti
2024-02-28 15:10 ` patchwork-bot+linux-riscv [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=170913302975.9913.9405105778490456621.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vadim.shakirov@syntacore.com \
--cc=will@kernel.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