Hello:
This series was applied to riscv/linux.git (fixes)
by Nicolas Schier <[email protected]>:
On Tue, 14 Oct 2025 15:05:15 +0200 you wrote:
> The current logic to inherit -m32/-m64 from the kernel build only works
> for a few architectures. It does not handle byte order differences,
> architectures using different compiler flags or different kinds of ABIs.
>
> Introduce a per-architecture override mechanism to set CC_CAN_LINK and
> the flags used for userprogs.
>
> [...]
Here is the summary with links:
- [v2,01/10] kbuild: don't enable CC_CAN_LINK if the dummy program generates
warnings
https://git.kernel.org/riscv/c/d81d9d389b9b
- [v2,02/10] init: deduplicate cc-can-link.sh invocations
https://git.kernel.org/riscv/c/80623f2c83d7
- [v2,03/10] kbuild: allow architectures to override CC_CAN_LINK
(no matching commit)
- [v2,04/10] riscv: Implement custom CC_CAN_LINK
(no matching commit)
- [v2,05/10] s390: Implement custom CC_CAN_LINK
(no matching commit)
- [v2,06/10] powerpc: Implement custom CC_CAN_LINK
(no matching commit)
- [v2,07/10] MIPS: Implement custom CC_CAN_LINK
(no matching commit)
- [v2,08/10] x86/Kconfig: Implement custom CC_CAN_LINK
(no matching commit)
- [v2,09/10] sparc: Implement custom CC_CAN_LINK
(no matching commit)
- [v2,10/10] kbuild: simplify CC_CAN_LINK
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
