Re: [PATCH v1] riscv: kvm: Use endian-specific __lelong for NACL shared memory
| Newsgroups | org.infradead.lists.kvm-riscv,org.infradead.lists.linux-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178246208372.3816447.9810005317307164502.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to riscv/linux.git (fixes) by Anup Patel <[email protected]>: On Mon, 8 Jun 2026 23:52:52 +0800 you wrote: > When compiling with sparse enabled (C=2), bitwise type warnings are > triggered in the RISC-V KVM implementation. This occurs because the > user-space data unboxing macro '__get_user_asm' performs implicit > casting on restricted types without forcing the compiler's compliance. > > Additionally, raw 'unsigned long *' pointers are used to access the > SBI NACL shared memory, whereas the RISC-V SBI specification mandates > that these structures must follow little-endian byte ordering. > > [...] Here is the summary with links: - [v1] riscv: kvm: Use endian-specific __lelong for NACL shared memory https://git.kernel.org/riscv/c/52738352a6f2 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html -- kvm-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kvm-riscv