From: patchwork-bot+linux-riscv@kernel.org
To: Andreas Schwab <schwab@suse.de>
Cc: linux-riscv@lists.infradead.org, conor@kernel.org,
palmer@dabbelt.com, cuiyunhui@bytedance.com, bjorn@rivosinc.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: use KERN_INFO in do_trap
Date: Thu, 04 Apr 2024 19:40:29 +0000 [thread overview]
Message-ID: <171225962903.17194.5283335335364983285.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <mvmy1aegrhm.fsf@suse.de>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 19 Mar 2024 16:40:05 +0100 you wrote:
> Print the instruction dump with info instead of emergency level. The
> unhandled signal message is only for informational purpose.
>
> Fixes: b8a03a634129 ("riscv: add userland instruction dump to RISC-V splats")
> Signed-off-by: Andreas Schwab <schwab@suse.de>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: use KERN_INFO in do_trap
https://git.kernel.org/riscv/c/dd33e5dc7247
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Andreas Schwab <schwab@suse.de>
Cc: linux-riscv@lists.infradead.org, conor@kernel.org,
palmer@dabbelt.com, cuiyunhui@bytedance.com, bjorn@rivosinc.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: use KERN_INFO in do_trap
Date: Thu, 04 Apr 2024 19:40:29 +0000 [thread overview]
Message-ID: <171225962903.17194.5283335335364983285.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <mvmy1aegrhm.fsf@suse.de>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 19 Mar 2024 16:40:05 +0100 you wrote:
> Print the instruction dump with info instead of emergency level. The
> unhandled signal message is only for informational purpose.
>
> Fixes: b8a03a634129 ("riscv: add userland instruction dump to RISC-V splats")
> Signed-off-by: Andreas Schwab <schwab@suse.de>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> [...]
Here is the summary with links:
- [v2] riscv: use KERN_INFO in do_trap
https://git.kernel.org/riscv/c/dd33e5dc7247
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-04-04 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 15:40 [PATCH v2] riscv: use KERN_INFO in do_trap Andreas Schwab
2024-03-19 15:40 ` Andreas Schwab
2024-03-19 19:46 ` Atish Patra
2024-03-19 19:46 ` Atish Patra
2024-03-20 2:20 ` [External] " yunhui cui
2024-03-20 2:20 ` yunhui cui
2024-04-04 13:41 ` Andreas Schwab
2024-04-04 13:41 ` Andreas Schwab
2024-04-04 14:45 ` Palmer Dabbelt
2024-04-04 14:45 ` Palmer Dabbelt
2024-04-04 19:40 ` patchwork-bot+linux-riscv [this message]
2024-04-04 19:40 ` patchwork-bot+linux-riscv
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=171225962903.17194.5283335335364983285.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=conor@kernel.org \
--cc=cuiyunhui@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=schwab@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.