From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] RISC-V: make ARCH_THEAD preclude XIP_KERNEL
Date: Wed, 05 Jul 2023 20:42:04 +0000 [thread overview]
Message-ID: <168858972422.10612.1710967993948363831.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230628-left-attractor-94b7bd5fbb83@wendy>
Hello:
This patch was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 28 Jun 2023 08:12:30 +0100 you wrote:
> Randy reported build errors in linux-next where XIP_KERNEL was enabled.
> ARCH_THEAD requires alternatives to support the non-standard ISA
> extensions used by the THEAD cores, which are mutually exclusive with
> XIP kernels. Clone the dependency list from the Allwinner entry, since
> Allwinner's D1 uses T-Head cores with the same non-standard extensions.
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
> Link: https://lore.kernel.org/all/ab38f6af-cb68-a918-1a63-2e7c927a8ffc@infradead.org/
> Fixes: da47ce003963 ("riscv: Add the T-HEAD SoC family Kconfig option")
> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V: make ARCH_THEAD preclude XIP_KERNEL
https://git.kernel.org/soc/soc/c/2fa4139f3e48
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-07-05 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 7:12 [GIT PULL] RISC-V: make ARCH_THEAD preclude XIP_KERNEL Conor Dooley
2023-07-05 20:42 ` patchwork-bot+linux-soc [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=168858972422.10612.1710967993948363831.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=soc@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