From: patchwork-bot+linux-riscv@kernel.org
To: Charles Mirabile <cmirabil@redhat.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, charlie@rivosinc.com
Subject: Re: [PATCH v1 0/1] fix riscv runtime constant support
Date: Wed, 11 Jun 2025 01:30:28 +0000 [thread overview]
Message-ID: <174960542825.2762376.5266886940672974555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250530211422.784415-1-cmirabil@redhat.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@dabbelt.com>:
On Fri, 30 May 2025 17:14:21 -0400 you wrote:
> I discovered that something broke basic booting on riscv64 for a nommu
> kernel with a minimal configuration running on qemu between 6.13 and
> current master. The symptom was that the kernel would hang and print
> nothing instead of booting normally. I bisected my way to:
>
> commit a44fb5722199 ("riscv: Add runtime constant support")
>
> [...]
Here is the summary with links:
- [v1,1/1] riscv: fix runtime constant support for nommu kernels
https://git.kernel.org/riscv/c/8d90d9872eda
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-06-11 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 21:14 [PATCH v1 0/1] fix riscv runtime constant support Charles Mirabile
2025-05-30 21:14 ` [PATCH v1 1/1] riscv: fix runtime constant support for nommu kernels Charles Mirabile
2025-05-31 2:35 ` Charlie Jenkins
2025-05-31 2:54 ` Charles Mirabile
2025-05-31 3:07 ` Charles Mirabile
2025-06-02 20:53 ` Charlie Jenkins
2025-06-02 20:53 ` Charlie Jenkins
2025-06-10 22:25 ` Palmer Dabbelt
2025-06-11 1:30 ` 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=174960542825.2762376.5266886940672974555.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cmirabil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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