From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel@sholland.org>
Cc: linux-riscv@lists.infradead.org, heiko@sntech.de,
jszhang@kernel.org, palmer@dabbelt.com, ajones@ventanamicro.com,
christoph.muellner@vrull.eu, conor.dooley@microchip.com,
guoren@kernel.org, heiko.stuebner@vrull.eu, nathan@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: Fix alternatives issues on for-next
Date: Wed, 15 Feb 2023 15:00:20 +0000 [thread overview]
Message-ID: <167647322042.11521.13482164945173632656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230212021534.59121-1-samuel@sholland.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sat, 11 Feb 2023 20:15:31 -0600 you wrote:
> Several people have reported that D1 fails to boot on linux-next.
> Patch 1 fixes a bug where early alternative patching used the wrong
> address. Patch 2 fixes a separate issue where the Zbb alternatives
> are incorrectly applied based on the 'C' extension instead of Zbb.
>
>
> Samuel Holland (2):
> riscv: Fix early alternative patching
> riscv: Fix Zbb alternative IDs
>
> [...]
Here is the summary with links:
- [1/2] riscv: Fix early alternative patching
https://git.kernel.org/riscv/c/bfd6fc5d8014
- [2/2] riscv: Fix Zbb alternative IDs
https://git.kernel.org/riscv/c/d5a7fab7859d
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:[~2023-02-15 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 2:15 [PATCH 0/2] riscv: Fix alternatives issues on for-next Samuel Holland
2023-02-12 2:15 ` [PATCH 1/2] riscv: Fix early alternative patching Samuel Holland
2023-02-12 15:48 ` Conor Dooley
2023-02-13 1:22 ` Guo Ren
2023-02-13 16:46 ` Jisheng Zhang
2023-02-12 2:15 ` [PATCH 2/2] riscv: Fix Zbb alternative IDs Samuel Holland
2023-02-12 15:20 ` Conor Dooley
2023-02-12 16:31 ` Andrew Jones
2023-02-13 1:19 ` Guo Ren
2023-02-12 15:09 ` [PATCH 0/2] riscv: Fix alternatives issues on for-next Conor Dooley
2023-02-13 1:23 ` Guo Ren
2023-02-15 14:56 ` Palmer Dabbelt
2023-02-15 15: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=167647322042.11521.13482164945173632656.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=christoph.muellner@vrull.eu \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=heiko.stuebner@vrull.eu \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=samuel@sholland.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