From: patchwork-bot+linux-riscv@kernel.org
To: Guo Ren <guoren@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@rivosinc.com,
conor.Dooley@microchip.com, heiko@sntech.de,
linux-kernel@vger.kernel.org, crash-utility@redhat.com,
guoren@linux.alibaba.com
Subject: Re: [PATCH -next V6 0/2] riscv: kexec: Fxiup crash_save percpu and
Date: Fri, 16 Dec 2022 19:37:50 +0000 [thread overview]
Message-ID: <167121947070.14925.11249878728419640630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209075513.532249-1-guoren@kernel.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 9 Dec 2022 02:55:11 -0500 you wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> Current riscv kexec can't crash_save percpu states and disable
> interrupts properly. The series fix them, make crash correct.
>
> v6:
> - Fixup checkpatch.pl problems
> - Remove Fixes tags and make the series as features
>
> [...]
Here is the summary with links:
- [-next,V6,1/2] riscv: kexec: EOI active and mask all interrupts in kexec crash path
https://git.kernel.org/riscv/c/b17d19a5314a
- [-next,V6,2/2] riscv: kexec: Make crash save multi harts' context
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-16 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 7:55 [PATCH -next V6 0/2] riscv: kexec: Fxiup crash_save percpu and guoren
2022-12-09 7:55 ` [PATCH -next V6 1/2] riscv: kexec: EOI active and mask all interrupts in kexec crash path guoren
2022-12-09 7:55 ` [PATCH -next V6 2/2] riscv: kexec: Make crash save multi harts' context guoren
2022-12-16 19:37 ` 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=167121947070.14925.11249878728419640630.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=conor.Dooley@microchip.com \
--cc=crash-utility@redhat.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.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