From: patchwork-bot+linux-riscv@kernel.org
To: None <takakura@valinux.co.jp>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
bjorn@kernel.org, paul.walmsley@sifive.com,
akpm@linux-foundation.org, aou@eecs.berkeley.edu,
apatel@ventanamicro.com, arnd@arndb.de, atishp@rivosinc.com,
bmeng.cn@gmail.com, conor.dooley@microchip.com,
daniel.thompson@linaro.org, samuel.holland@sifive.com,
sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
taka@valinux.co.jp
Subject: Re: [PATCH v2] RISC-V: Enable IPI CPU Backtrace
Date: Wed, 14 Aug 2024 14:10:34 +0000 [thread overview]
Message-ID: <172364463499.2278280.12370674777574036166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240718093659.158912-1-takakura@valinux.co.jp>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 18 Jul 2024 18:36:59 +0900 you wrote:
> From: Ryo Takakura <takakura@valinux.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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-08-14 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 9:36 [PATCH v2] RISC-V: Enable IPI CPU Backtrace takakura
2024-08-14 14: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=172364463499.2278280.12370674777574036166.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=arnd@arndb.de \
--cc=atishp@rivosinc.com \
--cc=bjorn@kernel.org \
--cc=bmeng.cn@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=daniel.thompson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.com \
--cc=sfr@canb.auug.org.au \
--cc=taka@valinux.co.jp \
--cc=takakura@valinux.co.jp \
/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