From: patchwork-bot+linux-riscv@kernel•org
To: =?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1•codeaurora.org
Cc: linux-riscv@lists•infradead.org, nathan@kernel•org,
nicolas.schier@linux•dev, nsc@kernel•org, pjw@kernel•org,
palmer@dabbelt•com, aou@eecs•berkeley.edu, alex@ghiti•fr,
hca@linux•ibm.com, gor@linux•ibm.com, agordeev@linux•ibm.com,
borntraeger@linux•ibm.com, svens@linux•ibm.com,
maddy@linux•ibm.com, mpe@ellerman•id.au, npiggin@gmail•com,
christophe.leroy@csgroup•eu, tsbogend@alpha•franken.de,
tglx@linutronix•de, mingo@redhat•com, bp@alien8•de,
dave.hansen@linux•intel.com, x86@kernel•org, hpa@zytor•com,
davem@davemloft•net, andreas@gaisler•com,
linux-kbuild@vger•kernel.org, linux-kernel@vger•kernel.org,
masahiroy@kernel•org, linux-s390@vger•kernel.org,
linuxppc-dev@lists•ozlabs.org, linux-mips@vger•kernel.org,
sparclinux@vger•kernel.org
Subject: Re: [PATCH v2 00/10] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags
Date: Fri, 20 Feb 2026 04:10:47 +0000 [thread overview]
Message-ID: <177156064779.189817.8600732238018283033.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251014-kbuild-userprogs-bits-v2-0-faeec46e887a@linutronix.de>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andreas Larsson <andreas@gaisler•com>:
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
prev parent reply other threads:[~2026-02-20 4:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 13:05 [PATCH v2 00/10] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 01/10] kbuild: don't enable CC_CAN_LINK if the dummy program generates warnings Thomas Weißschuh
2025-11-12 19:55 ` Nicolas Schier
2025-11-14 4:27 ` Nathan Chancellor
2025-11-14 13:43 ` Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 02/10] init: deduplicate cc-can-link.sh invocations Thomas Weißschuh
2025-11-12 19:56 ` Nicolas Schier
2025-11-14 4:28 ` Nathan Chancellor
2025-10-14 13:05 ` [PATCH v2 03/10] kbuild: allow architectures to override CC_CAN_LINK Thomas Weißschuh
2025-11-12 19:56 ` Nicolas Schier
2025-11-13 9:22 ` Thomas Weißschuh
2025-11-14 4:31 ` Nathan Chancellor
2025-10-14 13:05 ` [PATCH v2 04/10] riscv: Implement custom CC_CAN_LINK Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 05/10] s390: " Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 06/10] powerpc: " Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 07/10] MIPS: " Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 08/10] x86/Kconfig: " Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 09/10] sparc: " Thomas Weißschuh
2025-10-14 13:05 ` [PATCH v2 10/10] kbuild: simplify CC_CAN_LINK Thomas Weißschuh
2025-11-12 19:56 ` Nicolas Schier
2025-11-12 20:03 ` [PATCH v2 00/10] kbuild: userprogs: introduce architecture-specific CC_CAN_LINK and userprog flags Nicolas Schier
2025-11-13 9:31 ` Thomas Weißschuh
2025-11-14 4:22 ` Nathan Chancellor
2025-12-19 8:10 ` patchwork-bot+linux-riscv
2026-02-20 4:10 ` 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=177156064779.189817.8600732238018283033.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel$(echo .)org \
--cc==?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1$(echo .)codeaurora.org \
--cc=agordeev@linux$(echo .)ibm.com \
--cc=alex@ghiti$(echo .)fr \
--cc=andreas@gaisler$(echo .)com \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=borntraeger@linux$(echo .)ibm.com \
--cc=bp@alien8$(echo .)de \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=davem@davemloft$(echo .)net \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=masahiroy@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=nathan@kernel$(echo .)org \
--cc=nicolas.schier@linux$(echo .)dev \
--cc=npiggin@gmail$(echo .)com \
--cc=nsc@kernel$(echo .)org \
--cc=palmer@dabbelt$(echo .)com \
--cc=pjw@kernel$(echo .)org \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=svens@linux$(echo .)ibm.com \
--cc=tglx@linutronix$(echo .)de \
--cc=tsbogend@alpha$(echo .)franken.de \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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