From: patchwork-bot+linux-riscv@kernel.org
To: Mayuresh Chitale <mchitale@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
atishp@rivosinc.com, ajones@ventanamicro.com,
cleger@rivosinc.com, afd@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: sbi: Prefer SRST shutdown over legacy
Date: Mon, 17 Nov 2025 08:10:28 +0000 [thread overview]
Message-ID: <176336702899.2854411.10334925946163449436.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251114065808.304430-1-mchitale@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Fri, 14 Nov 2025 06:58:06 +0000 you wrote:
> Currently, the sbi_init() always attempts to register the legacy shutdown
> function as the sys-off handler which is fine when RISCV_SBI_V01 is not
> enabled. However, if RISCV_SBI_V01 is enabled in the kernel and the SBI
> v0.1 is not supported by the underlying SBI implementation then the
> legacy shutdown fails. Fix this by not registering the legacy shutdown
> when SRST shutdown is available.
>
> [...]
Here is the summary with links:
- riscv: sbi: Prefer SRST shutdown over legacy
https://git.kernel.org/riscv/c/7b090e7b910c
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:[~2025-11-17 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:58 [PATCH] riscv: sbi: Prefer SRST shutdown over legacy Mayuresh Chitale
2025-11-14 10:58 ` Anup Patel
2025-11-17 8: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=176336702899.2854411.10334925946163449436.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=afd@ti.com \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchitale@ventanamicro.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
/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