mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Rui Qi <qirui.001@bytedance.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	pjw@kernel.org, aou@eecs.berkeley.edu, alex@ghiti.fr,
	debug@rivosinc.com, martin@kaiser.cx, mindal@semihalf.com,
	fustini@kernel.org, kees@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: crash: Add crash hotplug support
Date: Mon, 05 Oct 2026 17:00:16 +0000	[thread overview]
Message-ID: <179121961677.1813719.4405826480158733209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910032619.2477279-1-qirui.001@bytedance.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Thu, 10 Sep 2026 11:26:19 +0800 you wrote:
> When CPUs or memory are hot-plugged on a running system, the crash
> dump's elfcorehdr -- which describes the available CPUs and memory to
> the capture kernel -- must be kept in sync, otherwise a crash after a
> hotplug event would produce a vmcore that does not reflect the current
> system topology.
> 
> Enable crash hotplug for RISC-V by selecting
> ARCH_SUPPORTS_CRASH_HOTPLUG and providing the three architecture hooks
> invoked through the override macros in <asm/kexec.h>:
> 
> [...]

Here is the summary with links:
  - [v2] riscv: crash: Add crash hotplug support
    https://git.kernel.org/riscv/c/dfc0c564b4b0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-10-05 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  3:26 Rui Qi
2026-10-05 17:00 ` 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=179121961677.1813719.4405826480158733209.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=debug@rivosinc.com \
    --cc=fustini@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=martin@kaiser.cx \
    --cc=mindal@semihalf.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=qirui.001@bytedance.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

all inboxes | Powered by JetHome®