[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172364463499.2278280.12370674777574036166.git-patchwork-notify@kernel.org>
Date: Wed, 14 Aug 2024 14:10:34 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: None <takakura@...inux.co.jp>
Cc: linux-riscv@...ts.infradead.org, palmer@...belt.com, bjorn@...nel.org,
paul.walmsley@...ive.com, akpm@...ux-foundation.org, aou@...s.berkeley.edu,
apatel@...tanamicro.com, arnd@...db.de, atishp@...osinc.com,
bmeng.cn@...il.com, conor.dooley@...rochip.com, daniel.thompson@...aro.org,
samuel.holland@...ive.com, sfr@...b.auug.org.au,
linux-kernel@...r.kernel.org, taka@...inux.co.jp
Subject: Re: [PATCH v2] RISC-V: Enable IPI CPU Backtrace
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.com>:
On Thu, 18 Jul 2024 18:36:59 +0900 you wrote:
> From: Ryo Takakura <takakura@...inux.co.jp>
>
> Add arch_trigger_cpumask_backtrace() which is a generic infrastructure
> for sampling other CPUs' backtrace using IPI.
>
> The feature is used when lockups are detected or in case of oops/panic
> if parameters are set accordingly.
>
> [...]
Here is the summary with links:
- [v2] RISC-V: Enable IPI CPU Backtrace
https://git.kernel.org/riscv/c/f15c21a3de1b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists