Re: [PATCH v2 00/10] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags
| Newsgroups | org.kernel.vger.sparclinux,org.infradead.lists.linux-riscv,org.kernel.vger.linux-kbuild,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips,org.kernel.vger.linux-s390,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <177156064779.189817.8600732238018283033.git-patchwork-notify@kernel.org> |
Hello: This series was applied to riscv/linux.git (fixes) by Andreas Larsson <[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 (no matching commit) - [v2,02/10] init: deduplicate cc-can-link.sh invocations (no matching commit) - [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 https://git.kernel.org/riscv/c/dc2f4d41a6b6 - [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